You send Bitcoin to a friend. The app says “transaction sent” — but the coins have not arrived. Minutes pass. You refresh, growing uneasy: has something gone wrong? Then, after a while, the payment appears. What happened in between is one of blockchain’s most important concepts: confirmations. Understanding them explains why crypto payments are not instant, how the network reaches agreement, and how many confirmations you actually need before considering a payment final. This guide starts from absolute zero — no technical background required.
The Core Problem Confirmations Solve
Digital money has a fundamental challenge: what stops someone spending the same coin twice? With physical cash, handing over a note ends your ownership. With digital files — infinitely copyable — the “double-spend” problem haunted digital cash for decades. Blockchains solve it through a shared, ordered ledger: transactions are grouped into blocks, and the network agrees on which block came first. Your transaction is not truly final until the network has agreed, collectively and redundantly, that it happened.
A “confirmation” is simply this: your transaction has been included in a block, and additional blocks have been built on top of it. One confirmation = included in one block. Six confirmations = five more blocks stacked on top. Each additional block makes rewriting history exponentially harder — and that stacking is what creates finality.
How Blocks and Confirmations Work, Step by Step
1. You broadcast. Your wallet sends the signed transaction to the network, where it waits in a queue (often called the mempool) with everyone else’s pending transactions.
2. A validator includes it. A miner or validator selects your transaction, bundles it with others into a new block, and adds that block to the chain. You now have one confirmation.
3. The chain grows. Roughly every ten minutes (Bitcoin) or twelve seconds (Ethereum), another block is added on top. Each new block buries your transaction deeper — two confirmations, three, and so on.
4. Finality emerges. To reverse your transaction, an attacker would need to rewrite your block and every block after it — redoing all that computational work faster than the honest network keeps extending the chain. After a few confirmations, this is computationally infeasible; after many, it is physically absurd. That infeasibility is what “confirmed” means.
Why Confirmations Take the Time They Take
Confirmation speed depends on three factors. Block time is structural: Bitcoin targets ten minutes per block, so six confirmations take about an hour on average. Network congestion matters enormously: when the queue is long, transactions offering higher fees get picked first — your low-fee transaction waits. This is the same dynamic as evening broadband slowdowns: shared capacity, peak demand, everything queues. Your fee determines your queue position: pay more, confirm sooner.
So “how long until confirmed?” has no single answer — it ranges from seconds (fast chains, high fees, quiet periods) to hours (congested Bitcoin, low fees, peak demand). Wallets estimate it; explorers show it live.
How Many Confirmations Do You Actually Need?
It depends on the stakes — this is about risk management, not ritual:
One confirmation is fine for small, trusted payments — buying a coffee with crypto, moving funds between your own wallets. The theoretical risk of reversal exists but is negligible against the cost of waiting.
Three to six confirmations is the standard for significant amounts — exchange deposits typically require several. Six Bitcoin confirmations (about an hour) is the traditional benchmark for large transfers, representing security far beyond what any attacker could practically overcome.
More for the paranoid (or the huge). Exchanges sometimes require dozens of confirmations for enormous deposits or for smaller, less-secure chains where rewriting history is cheaper. The principle scales: value at stake determines patience required.
The key insight: confirmations are not a bureaucratic delay — they are the mechanism of trust. Each one is the entire global network independently re-verifying your transaction’s place in history.
What Can Go Wrong: Stuck and Dropped Transactions
Stuck transactions. Set the fee too low during congestion and your transaction can sit unconfirmed for hours or days. Most wallets let you “bump” the fee to accelerate it. Patience plus fee-bumping resolves nearly all cases.
Dropped transactions. Some networks eventually evict long-unconfirmed transactions from the queue — the funds never left your wallet, so nothing is lost, but you need to rebroadcast. For background on how the technology is treated in the UK, see the FCA’s consumer guidance on cryptoassets and HMRC’s guidance on cryptoassets and tax.
Chain reorganisations. Rarely, the network briefly disagrees about the latest block and one version wins — transactions in the losing version return to the queue. This is why exchanges wait for multiple confirmations: one-confirmation finality can theoretically wobble; six-confirmation finality essentially cannot.
If a payment seems stuck, check its status on a blockchain explorer using the transaction ID — it shows confirmations, fee and queue position. That single habit resolves 90% of confirmation anxiety, much like verifying a phone transfer completed rather than assuming the worst: check the actual status before worrying, and you will almost always find the network is simply working through its queue.
Confirmations Across Different Blockchains
Every chain has its own rhythm. Bitcoin: ~10-minute blocks, six confirmations the norm for large amounts (~1 hour). Ethereum: ~12-second blocks, with exchanges typically wanting 12–35 confirmations (a few minutes). Fast chains finalise in seconds. The underlying principle never changes — stacked agreement creates finality — only the speed and the customary numbers differ. When using a new blockchain, check its standard confirmation expectations rather than assuming Bitcoin’s. And note an important nuance: some modern chains offer “instant finality” designs where validators explicitly finalise blocks rather than relying purely on accumulated work — the mechanism differs, but the purpose is identical: making the past unchangeable.
Conclusion
Blockchain confirmations are simply the network agreeing, block after stacked block, that your transaction happened — each one making reversal exponentially harder until finality is a practical certainty. They explain why crypto payments take time, why fees buy speed, and why patience scales with the amount at stake. The next time your transaction sits at “0 confirmations”, you will know it is not broken — it is queuing, and the queue is the security. Check the explorer, consider the fee, and let the blocks do their quiet, cumulative work.
Frequently Asked Questions
What does “1 confirmation” mean?
Your transaction has been included in one block on the blockchain. Additional blocks built on top increase the count — each one making the transaction harder to reverse.
How long do 6 Bitcoin confirmations take?
About an hour on average — Bitcoin targets one block every ten minutes. Congestion and fee levels cause variation; low-fee transactions during busy periods take longer.
Can a confirmed transaction be reversed?
After a few confirmations, reversal is computationally infeasible for any realistic attacker — that infeasibility is the point. This is why crypto payments, unlike card payments, have no chargebacks.
Why is my transaction stuck on zero confirmations?
Usually a fee too low for current congestion — it is queuing. Wait, or use your wallet’s fee-bump feature. Check the transaction ID on a blockchain explorer for its live status.
Do I need to wait for confirmations when receiving crypto?
For small amounts from trusted sources, one confirmation (or even zero, at your risk) suffices. For large or exchange-bound transfers, wait for the standard count — typically 3–6 for Bitcoin — before considering it final.
