When you send bitcoin, pressing “send” is not the moment the payment becomes final. Finality arrives one block at a time. A confirmation is simply a new block added on top of the block that contains your transaction, and each additional block makes a reversal exponentially harder. The question people actually care about — how many confirmations are enough — has no single answer, because the right number depends on the value at stake and on who absorbs the loss if the transaction is ever undone.
A payment with zero confirmations is still sitting in the mempool, the queue of broadcast transactions waiting for a miner. Until a block includes it, the sender can replace it with a higher-fee version or simply let it expire. One confirmation seals the payment into the chain. Because every block commits to the hash of the block before it, undoing a transaction means rebuilding that block and every block stacked on top of it, then outrunning the rest of the network, which keeps extending the honest chain.
That accumulating work is why confirmations, not the broadcast itself, decide when a payment is final. A single block takes about ten minutes on average, though any individual block can land in a minute or an hour. The network keeps that average in place by adjusting mining difficulty every 2,016 blocks, roughly every two weeks.
The six-block rule traces back to the Bitcoin whitepaper. In section 11, Satoshi Nakamoto worked out the probability that an attacker holding a given share of mining power could catch up and reverse a payment. Against an attacker with 10% of the hash rate, six confirmations leave a 0.024% chance of reversal; against 30%, the odds remain just over 13%. That arithmetic is what made six confirmations the conservative standard for large payments, and it is also why an attacker with more than half the hash rate can eventually overtake any number of confirmations.
Exchanges settle for fewer because a reversed deposit is their loss, not yours. Coinbase treats two confirmations as final for bitcoin, while Kraken and Gemini credit deposits after three. These are operational risk decisions rather than universal guarantees, and they change without notice, so it is worth checking the deposit screen before sending a large amount.
If a transaction looks stuck, the cause is almost always a fee priced below current demand. A block explorer such as mempool.space shows the fee rate you paid and the rate needed for the next block. The sender can use replace-by-fee (RBF) to rebroadcast the payment with a higher fee; the recipient can use child-pays-for-parent (CPFP) to pull both transactions into a block by spending the unconfirmed coins with a generous fee. Nodes drop unconfirmed transactions after roughly two weeks, returning the coins to the sender’s wallet.
For small, everyday payments, deep confirmation is unnecessary; the Lightning Network settles off-chain in seconds and reserves on-chain confirmations for opening and closing channels. For large transfers, waiting three to six blocks is a cheap hedge against a rare but real risk. The useful lesson is not a magic number but a habit: match the wait to the value, and let the chain’s accumulated work do the protecting.
Source: BTC-Pulse.