Confirmations are a measure of how deeply a cryptocurrency transaction is recorded in the currently accepted blockchain. In Bitcoin, the count includes the block containing the transaction and every block built after it, indicating how much blockchain history supports that inclusion.
How Confirmations Accumulate
A broadcast Bitcoin transaction may wait in nodes’ mempools—their pools of pending transactions—with zero confirmations. Miners select transactions for a candidate block, and network nodes check that the block and its transactions follow Bitcoin’s rules. Inclusion in an accepted block gives the transaction one confirmation. Each further block extending that chain adds another, so six confirmations means the containing block plus five later blocks.
Validation and confirmation depth answer different questions. Validation checks whether a transaction follows the rules, including whether its inputs can be spent. A growing count does not mean the payment is processed repeatedly; it means more accepted blocks have been built above its containing block.
Why Confirmation Depth Matters
Bitcoin uses proof of work to make rewriting accepted transaction history costly. Replacing a transaction’s block requires a competing valid chain with more accumulated work than the accepted chain. As more blocks build on top, an attacker generally needs to overcome more work to replace that history.
Waiting for more confirmations therefore reduces exposure to chain reorganizations and double-spending, where a conflicting transaction spends the same funds. It does not provide an unconditional guarantee of irreversibility. A reorganization can change the count or remove the transaction from the accepted chain, making it unconfirmed again.
Looking for liquidity, exploring on-ramp/off-ramp services, or seeking expert guidance?
Get startedHow Many Confirmations Are Needed
There is no universal acceptance threshold. The recipient or service chooses how long to wait based on the network, transaction value and risk tolerance. Six confirmations is a familiar Bitcoin convention, not a protocol requirement or a boundary beyond which every payment is safe. A recipient may require a different count, so check its policy rather than applying fixed rules for small or large payments. Other networks can use different finality models, making direct comparisons of block counts misleading.
Why Confirmation Times Vary
The wait has two parts: getting into a block and accumulating later confirmations. Bitcoin targets roughly ten minutes per block on average, but individual intervals vary substantially. A count-based waiting estimate is therefore not a deadline.
Congestion and a transaction’s fee rate relative to competing transactions can delay initial inclusion. A higher fee rate may make a transaction more attractive to miners, but it does not guarantee inclusion. Once the payment is in a block, its fee does not accelerate the creation of subsequent blocks.
Checking a Transaction’s Progress
To check progress, open the transaction details in your wallet or search its transaction ID in a blockchain explorer for the relevant network. Look for whether it is pending or included in a block and note the current confirmation count. Compare that count with the recipient’s stated requirement rather than relying only on a wallet’s “confirmed” label.
A payment can be confirmed on-chain before a service credits the deposit to your balance. If the required depth has been reached but credit is still pending, check the service’s deposit status or contact its support.
