Block Inclusion and Confirmations
The moment a miner includes your transaction in a block, it changes from "pending" to "confirmed." Each additional block built on top adds another confirmation, making your transaction exponentially harder to reverse.
Getting your transaction included in a block is the final step. Once mined, your transaction has "1 confirmation." Each additional block adds another confirmation, making reversal exponentially harder. Understanding confirmations helps you know when to consider a payment final.
What is Block Inclusion?
- •Definition: When a miner adds your transaction to a block they're mining.
- •First confirmation: The transaction is now in the blockchain (1 confirmation).
- •Not instant: Takes ~10 minutes on average (next block).
- •Fee dependent: Higher fees = higher priority = faster inclusion.
- •Permanent: Once in blockchain, transactions are extremely difficult to reverse.
Key Definitions:
- •Confirmation: Each block added after your transaction. 1 conf = in a block, 6 conf = buried 6 blocks deep.
- •Block inclusion: The moment a miner adds your transaction to a mined block.
- •Block time: Average time between blocks (~10 minutes).
- •Orphan block: A valid block that gets abandoned (reorganization). Rare but possible.
- •Chain reorganization (reorg): When the blockchain "reorganizes" and recent blocks are replaced.
- •Finality: The point at which reversal is practically/economically impossible.
How Miners Choose Transactions:
Block template construction: 1. Scan mempool: Look at all unconfirmed transactions. 2. Sort by fee: Prioritize highest sat/vB transactions. 3. Fill block: Add transactions until block is full (~1-4 MB). 4. Include coinbase: Add block reward transaction (subsidy + fees). 5. Calculate Merkle root: Hash all transactions into Merkle tree root. 6. Start mining: Try to find valid proof-of-work.
Timeline:
0:00 - Broadcast transaction
- •Transaction enters mempool
- •Status: Unconfirmed (0 confirmations)
- •Risk: High (could be double-spent in theory)
~10:00 - First block mined
- •Your transaction included in block 800,000
- •Status: 1 confirmation
- •Risk: Low (reorg possible but unlikely)
~20:00 - Second block mined
~60:00 - Sixth block mined
- •Block 800,005 builds on the chain
- •Status: 6 confirmations
- •Risk: Negligible (economically final)
Confirmation Recommendations:
0 confirmations (unconfirmed)
- •Risk: Moderate to high
- •Use case: Very small amounts, trusted parties
- •Example: Coffee purchase
1 confirmation (~10 min)
- •Risk: Low
- •Use case: Small to medium purchases
- •Example: Online shopping <$1,000
3 confirmations (~30 min)
- •Risk: Very low
- •Use case: Medium to large purchases
- •Example: Electronics, appliances
6 confirmations (~1 hour)
- •Risk: Negligible (industry standard)
- •Use case: Large purchases, exchange deposits
- •Example: Real estate down payment, moving $100K+
100+ confirmations
- •Risk: Essentially zero
- •Use case: Extremely high-value or critical
- •Example: Institutional treasury management
Zero-Confirmation Risk:
Why 0-conf is risky:
- •Transaction still in mempool
- •Not yet in blockchain
- •Sender could broadcast a conflicting transaction (double-spend)
- •Miner could include the conflicting transaction instead
Block Inclusion Process:
Miner perspective: 1. Receive transactions: Monitor P2P network and mempool. 2. Validate: Check all transaction rules. 3. Sort: Order by fee rate (highest first). 4. Construct candidate block: Fill with transactions up to size limit. 5. Add coinbase tx: Include reward (subsidy + all fees from included txs). 6. Calculate Merkle root: Hash tree of all transaction IDs. 7. Mine: Find nonce that produces valid proof-of-work hash. 8. Broadcast block: Send to network if successful.
Network perspective: 1. Receive block: Nodes get new block from mining node. 2. Verify block: Check proof-of-work, Merkle root, all transactions. 3. Accept if valid: Add to blockchain. 4. Update UTXO set: Mark inputs as spent, add outputs as unspent. 5. Remove txs from mempool: Included transactions are now confirmed.
Transaction Finality:
Levels of finality:
Broadcast (0 conf): Reversible. Not in blockchain yet.
1 confirmation: Mostly final. Reversal requires finding 2 blocks before next block (expensive).
6 confirmations: Economically final. Reversing would cost millions and be obvious.
100+ confirmations: Socially final. Entire Bitcoin community would reject a reorg this deep.
Key insight: Bitcoin finality is probabilistic, not absolute. But probability of reversal decreases exponentially with each block.
What Affects Confirmation Time?
1. Fee rate (sat/vB)
- •Dominant factor
- •Higher fee = faster confirmation
2. Mempool size
- •More congestion = need higher fee
3. Block variance
- •Blocks aren't exactly 10 minutes apart
- •Sometimes 1 minute, sometimes 30+ minutes
- •Average over time: 10 minutes
4. Transaction size
- •Larger transactions cost more for same fee rate
- •More inputs = larger size
5. Luck
- •Mining is probabilistic
- •Sometimes fast, sometimes slow
One confirmation is usually sufficient for small amounts. Six confirmations (about 60 minutes) is the standard for large transactions. After six blocks, reversing the transaction is practically impossible.
Test Your Knowledge
5 questions · Passing score: 75%
Enjoying these lessons?
Get a free Bitcoin lesson in your inbox every week. Join thousands of learners.
Free forever. No spam. Unsubscribe anytime.