In Bitcoin, “confirmed” is a dial rather than a switch. A payment that has just been mined is not in the same category as one buried under dozens of blocks, and treating the two as equivalent is a common way to misread settlement risk. Understanding what each new block actually contributes makes it easier to choose how long to wait.
What happens before the first block
A transaction is not confirmed when it appears in a wallet’s history. The wallet assembles it by spending previous outputs, signs it, and broadcasts it to the network, where nodes hold it in their memory pools until a miner places it in a solved block. That block is the transaction’s first confirmation, and everything before it is provisional.
A transaction waiting in the memory pool is visible to nodes but is not yet part of any block, which is why wallets and explorers label it unconfirmed until a miner includes it. How quickly that happens depends on the fee it offers relative to other pending transactions, not on a central scheduler.
Why depth matters more than the first confirmation
Bitcoin’s block chain is an ordered, timestamped record built to resist double-spending and tampering with earlier entries. Each transaction output can be spent only once, so a second attempt to spend the same satoshis is a forbidden double spend. The defense comes from proof of work: every block must demonstrate real computational effort, and because each block builds on the previous one, changing an old block means redoing the work of that block and every block after it.
That is why confirmation count is really block depth. One confirmation shows a transaction was included in the newest block, but that block can still be displaced if a competing chain overtakes it. Peers follow the chain with the most accumulated work and discard stale blocks. As more blocks are added, the cost of producing a longer competing chain rises, and a transaction’s position becomes more expensive to undo.
Because the first block that includes a transaction is its first confirmation, a payment shown as “2 confirmations” has been followed by one additional block. The count measures how deep a transaction sits in the chain, not a promise that its position can never change.
Reading the trade-off in practice
There is no single confirmation count that fits every situation. Services accepting high-value deposits commonly wait for several blocks, because the cost of reversing that much work far exceeds any plausible gain, while a small payment in a low-risk setting may be accepted sooner. The right number depends on the amount at stake, how long an attacker has to act, and what the recipient can afford to lose.
Confirmations also do not solve every problem. They make a transaction progressively harder to reverse, but they do not prove it was sent to the correct address, that a merchant has credited an account, or that no mistake was made upstream. Those risks live outside the block chain and need their own checks.
Why the security keeps compounding
The model is probabilistic rather than absolute. No central authority declares a transaction final; instead, accumulated proof of work makes reversal economically prohibitive over time. That is the trade Bitcoin offers: settlement confidence that grows with each block, purchased with the time and computing power honest miners commit to the chain.
Adapted from Bitcoin Block Chain Transactions: How Confirmations Build Security After a Transaction.