Definition
Confirmations are the count of blocks built on top of the block that contains a given Bitcoin transaction. A transaction in the latest block has one confirmation; each new block mined after it adds one more, and the deeper a transaction is buried, the harder it becomes to reverse.
Also known as: confirmation depth, block depth.
Bitcoin has no central authority that declares a payment “final.” Instead, finality is probabilistic and accrues over time. When your transaction first lands in a block, it is included but not yet deeply protected. Every subsequent block that extends the chain on top of it reburies it under more accumulated proof-of-work, making any attempt to rewrite history progressively more expensive and less likely to succeed.
How a confirmation is actually produced
A confirmation is not a separate action; it is simply another block being found. A pool or solo node assembles a candidate block from a block template, and mining hardware grinds the block header until a hash falls at or below the network difficulty target. The moment that share difficulty meets or exceeds the network difficulty, the block is found and broadcast to the network. Once it is accepted and references the previous block as its parent, every transaction in the chain below it gains exactly one more confirmation.
Because blocks arrive on average about every ten minutes, confirmations accumulate roughly at that pace. The common “six confirmations” convention — often quoted as around an hour — exists because six blocks of stacked work make a deliberate chain reorganization economically impractical for ordinary payment sizes. Smaller, low-risk transfers may be treated as settled with one confirmation; large or adversarial settings warrant more patience.
Why confirmations are never instant: reorgs and stale blocks
Confirmation depth matters because the chain tip is not always settled. Two miners can find valid blocks at nearly the same height before the network agrees, producing a temporary split that resolves under the longest-chain rule. Whichever branch accumulates the most work survives; the losing block becomes a stale block (or orphan block), and transactions that lived only in that branch drop back to the mempool to be reconfirmed.
A transaction with a single confirmation can still be undone if a competing branch wins. With each additional confirmation the odds of such a reversal shrink rapidly, which is precisely why merchants and exchanges wait for depth rather than trusting the freshest block. Propagation delay across the global node network is part of why these brief races happen at all.
Why confirmations matter to ASIC and home miners
For anyone running real hardware, confirmations connect directly to when you actually get paid. The first transaction in any block is the coinbase transaction, which pays the block reward to the miner. That coinbase payout is special: it cannot be spent until it has matured under a fixed depth of confirmations enforced by the protocol — one hundred blocks. If you ever solve a block solo with a desk-side Bitaxe or a fleet of S19s, that reward sits unspendable for roughly sixteen to seventeen hours of confirmations before it clears.
Maturity exists for the same reason confirmations exist everywhere else. If a freshly mined block is later orphaned in a reorg, its coinbase reward vanishes with it. Forcing newly minted coins to wait one hundred confirmations protects the network and downstream recipients from spending rewards that a reorg could erase. So whether you are pointed at a mining pool or running your own node, confirmation depth is the difference between a payout that exists on paper and one you can actually move.
This is also where decentralization quietly does its work. No clearinghouse stamps a transaction “final”; thousands of independent nodes simply keep building on the most-worked chain, and confirmation depth is the emergent, leaderless measure of agreement. Running your own node and verifying your own confirmations — rather than trusting a block explorer — is one more layer of sovereignty, and it pairs naturally with open, self-hosted hardware like the gear in our Bitaxe hub.
Related terms: Block Height, Longest-Chain Rule, Stale Block, Orphan Block, Coinbase Transaction, Block Time.
In Simple Terms
The number of blocks mined after a transaction, indicating how secure and irreversible it is.
Confirmations are the count of blocks built on top of the block that contains a given Bitcoin transaction. A transaction in the latest block has one confirmation; each new block mined after it adds one more, and the deeper a transaction is buried, the harder it becomes to reverse.
Also known as: confirmation depth, block depth.
Bitcoin has no central authority that declares a payment "final." Instead, finality is probabilistic and accrues over time. When your transaction first lands in a block, it is included but not yet deeply protected. Every subsequent block that extends the chain on top of it reburies it under more accumulated proof-of-work, making any attempt to rewrite history progressively more expensive and less likely to succeed.
How a confirmation is actually produced
A confirmation is not a separate action; it is simply another block being found. A pool or solo node assembles a candidate block from a block template, and mining hardware grinds the block header until a hash falls at or below the network difficulty target. The moment that share difficulty meets or exceeds the network difficulty, the block is found and broadcast to the network. Once it is accepted and references the previous block as its parent, every transaction in the chain below it gains exactly one more confirmation.
Because blocks arrive on average about every ten minutes, confirmations accumulate roughly at that pace. The common "six confirmations" convention — often quoted as around an hour — exists because six blocks of stacked work make a deliberate chain reorganization economically impractical for ordinary payment sizes. Smaller, low-risk transfers may be treated as settled with one confirmation; large or adversarial settings warrant more patience.
Why confirmations are never instant: reorgs and stale blocks
Confirmation depth matters because the chain tip is not always settled. Two miners can find valid blocks at nearly the same height before the network agrees, producing a temporary split that resolves under the longest-chain rule. Whichever branch accumulates the most work survives; the losing block becomes a stale block (or orphan block), and transactions that lived only in that branch drop back to the mempool to be reconfirmed.
A transaction with a single confirmation can still be undone if a competing branch wins. With each additional confirmation the odds of such a reversal shrink rapidly, which is precisely why merchants and exchanges wait for depth rather than trusting the freshest block. Propagation delay across the global node network is part of why these brief races happen at all.
Why confirmations matter to ASIC and home miners
For anyone running real hardware, confirmations connect directly to when you actually get paid. The first transaction in any block is the coinbase transaction, which pays the block reward to the miner. That coinbase payout is special: it cannot be spent until it has matured under a fixed depth of confirmations enforced by the protocol — one hundred blocks. If you ever solve a block solo with a desk-side Bitaxe or a fleet of S19s, that reward sits unspendable for roughly sixteen to seventeen hours of confirmations before it clears.
Maturity exists for the same reason confirmations exist everywhere else. If a freshly mined block is later orphaned in a reorg, its coinbase reward vanishes with it. Forcing newly minted coins to wait one hundred confirmations protects the network and downstream recipients from spending rewards that a reorg could erase. So whether you are pointed at a mining pool or running your own node, confirmation depth is the difference between a payout that exists on paper and one you can actually move.
This is also where decentralization quietly does its work. No clearinghouse stamps a transaction "final"; thousands of independent nodes simply keep building on the most-worked chain, and confirmation depth is the emergent, leaderless measure of agreement. Running your own node and verifying your own confirmations — rather than trusting a block explorer — is one more layer of sovereignty, and it pairs naturally with open, self-hosted hardware like the gear in our Bitaxe hub.
Related terms: Block Height, Longest-Chain Rule, Stale Block, Orphan Block, Coinbase Transaction, Block Time.