What Are Block Confirmations?
A block confirmation occurs every time a new block is mined (or proposed and attested) on top of the block containing your transaction. Each additional confirmation exponentially decreases the probability that your transaction could be reversed, reorganized, or double-spent. When you send a cryptocurrency transaction on most explorers and wallets, you will see a small number next to your transaction — that is the confirmation count.
In practical terms, one confirmation simply means your transaction was included in a block. Two confirmations mean another block was built on top of it, making it harder to reverse. Six confirmations mean six blocks were stacked on top, which is the widely accepted standard for Bitcoin. The deeper your transaction sits in the chain, the more secure it becomes because an attacker would need to produce an alternative chain that is longer — and that requires an enormous amount of computational work.
How Confirmations Work in Bitcoin
Bitcoin uses a Proof-of-Work (PoW) consensus mechanism. When a miner finds a valid block, it is broadcast to the network and nodes validate it. If another miner had been working on a competing block at the same height, a temporary fork occurs. The network eventually converges on the longest chain, and the blocks on the abandoned branch become “orphaned” — their transactions are not included in the canonical chain.
This is why multiple confirmations matter. With only one confirmation, there is a non-trivial probability that your block could be orphaned and your transaction effectively undone. Satoshi Nakamoto’s original Bitcoin whitepaper analyzed this using the probability of an attacker catching up from z blocks behind. The math works out roughly as follows:
- 1 confirmation (~10 minutes): There is still a meaningful chance of reversal if a powerful miner produces an alternative block.
- 3 confirmations (~30 minutes): The probability drops significantly. Many exchanges use this threshold for mid-value deposits.
- 6 confirmations (~60 minutes): The probability of reversal becomes vanishingly small — approximately 0.1% even against an attacker controlling 10% of the network hash rate. This is the gold standard for high-value transactions like buying a house or settling large OTC trades.
The exact probability of reversal depends on the attacker’s share of total hash rate. If an attacker controls 30% of the hash rate, six confirmations still provide a strong guarantee. If they control 50%+, no number of confirmations is safe (this is the 51% attack scenario). For a typical user transacting against the global network, six confirmations is considered effectively final.
Some services accept fewer confirmations for lower-value transactions. A coffee purchase might clear with just one confirmation, while a $100,000 wire-equivalent transfer would require six. It is a risk/reward tradeoff calibrated to the value at stake.
How Confirmations Work in Ethereum
Ethereum’s confirmation model is different from Bitcoin’s in important ways. Before the Merge (September 2022), Ethereum used Proof-of-Work and had similar probabilistic finality to Bitcoin — the community generally recommended 12 to 30 confirmations for high-value transactions, which took 3 to 6 minutes (given Ethereum’s ~12 second block time).
After the Merge, Ethereum switched to Proof-of-Stake with a mechanism called Casper FFG (Friendly Finality Gadget). Under this system, blocks become “finalized” through a two-stage process:
- Justified: A block is justified when two consecutive epochs (each epoch is 32 slots, approximately 6.4 minutes) of blocks have been attested by validators representing at least two-thirds of the total staked ETH.
- Finalized: A justified epoch becomes finalized when another justified epoch follows it. Once a block is finalized, it cannot be reversed without destroying at least one-third of all staked ETH (worth billions of dollars).
This means Ethereum has a concept of absolute finality that Bitcoin lacks. After approximately 12–14 minutes (about 2 epochs), a block on Ethereum is finalized — not just probabilistically secure but cryptographically guaranteed. An attacker would need to burn over $20 billion worth of ETH to reverse a finalized block, which is economically infeasible.
For practical purposes, most Ethereum services consider a transaction safe after:
- 12 confirmations (~2.5 minutes): Standard for most exchanges and DeFi protocols.
- 25–30 confirmations (~5–6 minutes): Used for larger transfers by more conservative services.
- Finalized (~12–14 minutes): The gold standard — irreversible under normal conditions.
Confirmations on Layer 2 and Alternative Chains
Layer 2 solutions and alternative blockchains have their own confirmation paradigms:
- Optimistic Rollups (Arbitrum, Optimism): Transactions are confirmed on L2 within seconds, but they inherit L1 security through a challenge period (typically 7 days). Full security guarantee requires waiting for the challenge window to expire.
- Zero-Knowledge Rollups (zkSync, StarkNet): Transactions are confirmed on L2 quickly, with validity proofs submitted to L1 periodically. Finality is faster than optimistic rollups because proofs are deterministic, not dependent on a challenge period.
- Solana: Uses a Proof-of-Stake mechanism called Tower BFT. The network achieves finality after approximately 32 confirmations (roughly 13 seconds of block production). However, the Solana network occasionally experiences cluster restarts during extreme outages, which can technically reverse recent confirmations.
- Binance Smart Chain (BNB Chain): Uses Proof-of-Staked-Authority with a 3-second block time. Finality is achieved after approximately 15 confirmations (45 seconds), though the smaller validator set means the trust assumption differs from Ethereum.
Why Confirmations Matter for DeFi
In DeFi applications, understanding block confirmations is critical because smart contracts execute automatically. If you deposit funds into a lending protocol after only one confirmation and that block gets reorganized, the smart contract may not recognize your deposit. Most DeFi protocols on Ethereum handle this gracefully by using the block.timestamp and transaction inclusion guarantees, but the UX risk is real — you might see a pending transaction that never lands.
For cross-chain bridges, confirmations are even more important. A bridge locking your ETH on mainnet might require 15-30 confirmations before minting the corresponding tokens on the destination chain. If you see a bridge transaction stuck at “Waiting for confirmations,” this is the mechanism at work — the bridge is waiting for sufficient probabilistic security before committing to the mint on the other side.
Confirmation Count by Chain
| Chain | Recommended Confirmations | Approximate Time |
|---|---|---|
| Bitcoin | 6 | ~60 minutes |
| Ethereum (PoS) | 12–30 (or wait for finality) | ~2.5–14 minutes |
| Bitcoin Cash | 6 | ~60 minutes |
| Litecoin | 6 | ~30 minutes |
| Solana | 32 | ~13 seconds |
| BNB Chain | 15 | ~45 seconds |
| Polygon | 128 | ~6 minutes |
Common Pitfalls
- Rushing transactions: Sending funds after only one confirmation and then spending or trading them before sufficient security is achieved.
- Mixing up chain confirmation standards: Bitcoin’s 6-confirmation standard applied to Ethereum (which has a much faster block time) would be unnecessarily conservative.
- Ignoring L1 security on L2s: A fast L2 confirmation does not mean your transaction is as secure as an L1 confirmation. Always understand the security model of the chain you are using.
- Finality vs. confirmation: On proof-of-stake chains, finality is a distinct concept from mere block depth. A block can have 100 confirmations but not yet be finalized.