Bitcoin Confirmations: How Transactions Become Final
Bitcoin confirmations record transactions permanently on the blockchain. Learn what they are, how many you need, and why they matter for security.
Key takeaways
- A Bitcoin confirmation is the process by which a transaction is permanently recorded into a block on the blockchain. Each new block added on top counts as one additional confirmation.
- Confirmations are layers of cryptographic certainty that accumulate over time, making a transaction progressively harder to reverse.
- The number of confirmations needed depends on context, with different thresholds for small payments, exchange deposits, and large transfers.
- Bitcoin's confirmation model trades speed for security.
A Bitcoin confirmation occurs when a transaction is included in a block and that block is added to the blockchain. Each new block added after it counts as one more confirmation – a signal that the network has verified and accepted the transaction.
Understanding how confirmations work helps you know what to expect when sending or receiving Bitcoin, and why some platforms make you wait longer than others.
What Is a Bitcoin Confirmation?
| A Bitcoin confirmation is a record that a transaction has been permanently written into the blockchain. When you send Bitcoin, your transaction gets broadcast to the network, picked up by miners, bundled into a block, and only then confirmed. |
The first time that block is added to the chain, your transaction has 1 confirmation. Every block mined on top of it adds another.
Think of each confirmation as another layer of cement poured over the record – the more layers, the harder it becomes to dig back and alter anything.
Why Confirmations Matter in Bitcoin Transactions
| Without confirmations, there's no way to know whether a transaction is legitimate or an attempt to spend the same Bitcoin twice – a scenario known as a double-spend attack. |
Confirmations solve this problem by requiring real computational work. Miners must expend energy and computing power to add a block to the chain – a process governed by Bitcoin's consensus mechanism.
Reversing a confirmed transaction would mean redoing all that work and outpacing every honest miner on the network simultaneously. The more confirmations a transaction has, the more computationally expensive it becomes to undo.
This is also why exchanges, merchants, and payment processors set minimum confirmation thresholds before crediting funds.
How the Bitcoin Confirmation Process Works
The confirmation process moves through three distinct states:
Each state carries a different level of finality and risk. |
0 Confirmations vs 1 Confirmation
When you send Bitcoin, your transaction enters the Bitcoin mempool (memory pool) – a waiting room where unconfirmed transactions sit until a miner picks them up. At this stage, your transaction has 0 confirmations.
A transaction with 0 confirmations is called unconfirmed.
- It's visible on the network, but it hasn't been finalized.
- It can still be replaced or dropped, especially if the attached fee is too low.
Once a miner bundles your transaction into a block and that block is added to the blockchain, you have 1 confirmation. The transaction is now on-chain and reversing it would require re-mining that block.
Why Each Additional Confirmation Increases Security
Every block added after yours makes reversal progressively harder.
To undo a transaction with 3 confirmations, an attacker would need to secretly re-mine 3 blocks faster than the entire rest of the network is mining and then broadcast the longer chain to replace it.
Bitcoin's protocol always recognizes the chain with the most accumulated proof-of-work as the valid one. This means an attacker needs not just one successful block, but a sustained lead over the entire honest network.
The further back a transaction is buried, the more computationally impossible that becomes.
What Happens After 6 Confirmations?
Six confirmations have become the widely accepted standard for treating a Bitcoin transaction as final.
At this point, reversing the transaction would require controlling the majority of the network's hash rate for an extended period – an effort that research from Coin Metrics estimated would require purchasing roughly 7 million ASIC mining rigs at a cost of around $20 billion.
For the vast majority of transactions, 6 confirmations represents a point of practical irreversibility. Some high-value transfers may wait for more, but the marginal security gain beyond 6 decreases significantly.
If you want a full picture of what happens between broadcast and confirmation, the Bitcoin transaction lifecycle covers each step in detail.
How Many Bitcoin Confirmations Are Needed?
The right number of confirmations depends on the value of the transaction and the policies of the platform involved. Here's a general reference:
Confirmations | Approx. time | Recommended for |
| 0 | Instant | Trusted parties only (high risk) |
| 1 | ~10 min | Small peer-to-peer payments under $1,000 |
| 3 | ~30 min | Mid-size payments $1,000–$10,000; most exchange deposits |
| 6 | ~60 min | Large transfers $10,000–$1,000,000; industry standard |
| 6+ | 60+ min | High-value institutional transfers over $1,000,000 |
Small payments
For everyday low-value transfers, like paying a friend or buying a small amount of goods, 1 confirmation is generally considered sufficient. The economic incentive to reverse a small transaction is too low to justify the cost of an attack.
Exchange deposits and withdrawals
Most major cryptocurrency exchanges require 3 confirmations before a Bitcoin deposit is credited.
For example, Coinbase requires 3 confirmations while Binance requires 1 confirmation for deposits and 2 for withdrawals. These thresholds reflect each platform's own risk tolerance.
Large Bitcoin transfers
For transfers in the range of tens or hundreds of thousands of dollars, waiting for 6 confirmations is standard practice.
Some institutional custodians and OTC desks may require even more for seven-figure transactions – not because 6 is unsafe, but because the cost-benefit calculation justifies extra caution at that scale.
How Long Does a Bitcoin Confirmation Take?
Bitcoin's protocol is designed to produce one new block approximately every 10 minutes. In practice, actual confirmation times vary based on network congestion, transaction fees, and natural randomness in the Bitcoin mining process.
Confirmations | Target time | Real-world range |
| 1 | ~10 min | 1 min – 60+ min |
| 3 | ~30 min | 10 min – 2+ hours |
| 6 | ~60 min | 30 min – several hours |
According to YCharts data, the average Bitcoin confirmation time was around 18.7 minutes on May 13, 2025, but had spiked to 34.2 minutes just days earlier. During heavy mempool congestion periods, average confirmation times have exceeded 90 minutes.
Two main factors affect your wait time:
- Transaction fee: Miners prioritize transactions with higher fees. A low fee during a congested period may leave your transaction sitting in the mempool for hours. Paying a competitive fee is the single most effective way to speed up confirmation.
- Network congestion: Bitcoin's base layer can process around 7 transactions per second. When demand spikes, during market rallies or high-activity events, the mempool fills up and wait times increase. You can monitor current congestion at mempool.space.
If your transaction has been unconfirmed for more than a few hours, it may be stuck in the mempool. Some wallets support Replace-By-Fee (RBF), which lets you rebroadcast the transaction with a higher fee to jump the queue.
If your wallet doesn't support RBF, Child-Pays-For-Parent (CPFP) is another option. You create a new transaction spending the unconfirmed output with a high fee, incentivizing miners to confirm both at once.
How Bitcoin Confirmations Differ From Other Networks
Bitcoin's confirmation model is not the only approach to transaction finality. Different blockchains make different tradeoffs between speed, security, and decentralization.
Network | Block time | Finality time | Finality type | Security model |
| Bitcoin (BTC) | ~10 min | ~60 min (6 blocks) | Probabilistic | Proof of Work |
| Ethereum (ETH) | ~12 sec | ~12–15 min (2 epochs) | Economic (PoS checkpoints) | Proof of Stake |
| Solana (SOL) | ~400 ms | ~2–5 sec | Deterministic | PoH + PoS |
| Litecoin (LTC) | ~2.5 min | ~15 min (6 blocks) | Probabilistic | Proof of Work |
| XRP Ledger | ~3–5 sec | ~3–5 sec | Deterministic | Federated consensus |
The most significant difference across networks is the type of finality each one uses:
- Probabilistic finality (Bitcoin, Litecoin): No single moment of irreversibility – each confirmation makes reversal exponentially more costly. Security is a function of depth, not a binary switch.
- Economic finality (Ethereum): Transactions finalize through validator checkpoints. Once two-thirds of validators attest, reversal becomes economically catastrophic rather than just technically difficult.
- Deterministic finality (Solana, XRP): The network reaches explicit consensus before accepting a transaction – confirmed means final, with no probabilistic gray area.
Bitcoin's slower model is a deliberate tradeoff: security doesn't rely on any validator set, and the cost of reversal is grounded in real computational work rather than economic incentives.
Can Bitcoin Confirmations Be Reversed?
| Technically yes, but practically no. A transaction becomes harder to reverse with each confirmation. At 6+, the computational cost of undoing it exceeds any realistic economic incentive to try. |
1. Blockchain reorgs & double-spend attacks
A reorg happens when the network discovers a competing chain with more accumulated proof-of-work, causing some blocks to be orphaned and their transactions returned to the mempool.
Most reorgs are natural and brief – two miners finding a block simultaneously – and resolve within a block or two. In early 2026, Bitcoin experienced a rare two-block reorg that resolved automatically without any user impact.
A double-spend attack deliberately exploits this: an attacker sends Bitcoin, waits for confirmation, then broadcasts a secretly mined longer chain to erase the payment.
On Bitcoin, this would require controlling over 51% of the network's hash rate, estimated to cost upwards of $10 billion in 2026. Between 2018 and 2024, 85% of successful 51% attacks hit nascent chains with market caps below $100 million, not established networks like Bitcoin.
2. Are 0-confirmation transactions safe?
A 0-conf transaction is visible in the mempool but not yet final – it can still be replaced before a miner picks it up.
For small trusted payments, it may be acceptable. But for any transaction where value is delivered before confirmation, waiting for at least 1 block is the safer default.
The Lightning Network sidesteps this entirely by moving small, frequent payments off-chain – settling channels on the Bitcoin base layer while enabling instant transfers between them.
One underappreciated aspect of Bitcoin's confirmation model: it's one of the few systems in finance where the cost of fraud is public and auditable in real time. Anyone can look up the current hash rate and calculate, roughly, what it would cost to reverse a transaction of any given depth. Whether that tradeoff is worth a 60-minute wait depends on what you're sending, and to whom.
Sources and Further Reading
- Bitcoin Whitepaper – Satoshi Nakamoto
- Chain Reorganization – Bitcoin Wiki
- Blockchain.com – Average Confirmation Time Chart
- What Is Finality in Blockchain? – CoinTelegraph
- 51% Attack Vulnerability of Nascent Blockchains – Springer Nature (2026)
- Chain Reorganization Explained – LearnMeABitcoin
- mempool.space – Real-Time Bitcoin Mempool Explorer
FAQ About Bitcoin Confirmations
Not guaranteed, but strongly correlated. A higher fee makes your transaction more attractive to miners competing to fill the next block. During spikes in network activity, paying above the median fee is often necessary to avoid significant delays.
