A Bitcoin confirmation is one additional block added to the blockchain on top of the block that recorded your transaction. Each new block buries your transaction deeper in the chain, making it progressively harder to reverse, though never mathematically impossible under all conditions.
This guide covers on-chain Bitcoin confirmations only, not Lightning Network payments. It is written for people sending or receiving BTC who want to understand what confirmation counts mean, how to decide when enough is enough, what a chain reorganization is and how often it actually happens, and what to do when a transaction stalls. It does not cover trading strategy, tax guidance, or Bitcoin mining operations.
What is a Bitcoin block, and why do confirmations count blocks?
A block is a batch of validated Bitcoin transactions, sealed with a cryptographic proof of work and linked to every previous block through a chain of hashes. Confirmations count how many blocks have been added to the chain after your transaction's block. A confirmation count is simply a depth measurement in the blockchain.
This framing matters because the security of a confirmed transaction comes from the accumulated computational work behind it, not from the passage of time.
What a block contains:
Several hundred to several thousand validated transactions
A cryptographic reference (hash) to the previous block's header
A merkle root: a single hash summarizing all transactions in the block
A timestamp and difficulty target
The nonce the miner used to satisfy proof of work
The coinbase transaction paying the miner the block subsidy plus fees
Block height and the chain tip: Every block has a sequential position number called its block height. Block 0 is the genesis block (January 3, 2009). The chain tip is whichever block has the highest height on the longest chain: the one with the most accumulated proof of work. As of May 2026, Bitcoin's chain tip sits around block 948,000 (source: bitbo.io).
The 10-minute average is a target, not a timer. Bitcoin adjusts mining difficulty every 2,016 blocks (roughly two weeks) to keep the average block interval near 10 minutes. But individual blocks are random: some arrive in 30 seconds, others take 45 minutes. This variability is not a bug; it is an expected property of the Poisson process that governs block discovery. Plan for waits, not precise schedules.
For a deeper explanation of how blocks link together to form a tamper-resistant ledger, see our guide on how the Bitcoin blockchain works.
How are Bitcoin confirmations counted?
When your transaction is first included in a block, it has exactly 1 confirmation. Each subsequent block added to the chain increases that count by one. A transaction with 6 confirmations means there are 5 blocks on top of the block that included your transaction.
The lifecycle of a transaction
Before any block includes your transaction, it sits in the mempool, a pool of unconfirmed transactions broadcast across thousands of nodes waiting for miners to pick it up. At this stage the transaction has 0 confirmations, often labeled "pending" or "unconfirmed" in wallets.
Once a miner includes it in a valid block, you have 1 confirmation. The next block mined on top gives you 2. This continues indefinitely as long as the network keeps producing blocks.
Why wallets sometimes disagree temporarily
When a new block is found, it takes a few seconds to propagate across all nodes. During this window, some services may show N confirmations while others still show N-1. That discrepancy resolves within seconds as the new block propagates. If the discrepancy persists for minutes, check multiple block explorers; a short-lived chain competition (reorg) may be resolving.
Worked example with actual numbers
You send 0.05 BTC. It enters the mempool at 14:30 UTC. A miner includes it in block 945,001 at 14:42 UTC: 1 confirmation. Block 945,002 arrives at 14:53 UTC: 2 confirmations. Block 945,003 arrives at 15:06 UTC: 3 confirmations. If you're using an exchange that requires 3 confirmations for deposit credit, your funds would be credited around 15:06 UTC in this example, roughly 36 minutes after you sent the transaction.
To verify your transaction's confirmation count directly on-chain, use a block explorer and search by your transaction ID (txid). The explorer shows the block your transaction is in, how deep that block is, and whether the block is on the current best chain.
Why do more confirmations make a transaction harder to reverse?
Each confirmation represents real-world computational work expended by miners, specifically the proof of work mechanism at Bitcoin's core. To reverse a confirmed transaction, an attacker must redo that work plus outpace all honest miners producing new blocks simultaneously.
The math behind the 6-confirmation standard
Section 11 of the Bitcoin whitepaper contains the probability formula governing reversal risk. If an attacker controls 10% of total network hashrate and the receiver waits for 6 confirmations, the probability of a successful double-spend drops below 0.1% (en.bitcoin.it, Bitcoin Wiki "Confirmation"). This is where the 6-block threshold originated: not as a hard guarantee, but as a threshold that makes attack economically irrational under that hash power assumption.
With Bitcoin's May 2026 hashrate at close to 1,000 EH/s (exahashes per second) (source: bitbo.io), the energy and hardware cost of controlling even 10% is enormous. At 40% hash power control, the attacker would need 60 confirmations to reduce success probability below 1%. For typical deposits and standard transaction amounts, the 6-confirmation threshold covers real-world risk adequately.
The concrete analogy
Each block is a layer of hardened concrete poured over your transaction. One layer can theoretically be broken up. Six layers require an excavation project that costs more than any rational attacker could profit from reversing a typical deposit. Sixty layers are a fortress wall.
What probabilistic finality actually means
Bitcoin offers probabilistic finality: certainty grows with each confirmation but never technically reaches 100%. This is different from irreversibility after a legal settlement or a bank chargeback deadline. For practical purposes at normal transaction sizes and after 6 confirmations, the difference between "probabilistic" and "certain" is academic.
What is a chain reorganization (reorg) and should you worry about it?
A chain reorganization is when the Bitcoin network switches from its current chain tip to a competing chain that has accumulated more proof of work. Blocks on the abandoned branch become stale: they were valid under the rules, but they are no longer part of the main chain.
Reorgs happen because of natural network latency, not attacks. Two miners in different parts of the world can find valid blocks within seconds of each other. Nodes near one miner see that block first; nodes near the other see the competing block. The network briefly runs two competing chain tips at the same height until one branch gets a new block added first, tipping the accumulated-work balance.
How common are reorgs?
According to continuous node monitoring data from learnmeabitcoin.com, single-block reorgs occur approximately once every 45.6 days (once every 6,647 blocks), not once every 1-2 weeks as sometimes claimed. This is the most important calibration for users: shallow reorgs are routine network events, but they happen less often than many sources suggest.
Two-block reorgs are far rarer. Bitcoin's entire history contains a few dozen. The most recent example occurred on March 23, 2026, when Foundry USA and the competing pool pair AntPool + ViaBTC found valid blocks within 12 seconds of each other at block height 941,880. Foundry subsequently mined seven blocks in a row, making its branch the heaviest. AntPool and ViaBTC's blocks became stale. The network resolved the event automatically and completely. No transactions were harmed, no funds were at risk, and Bitcoin's price did not move significantly (source: CoinDesk).
Three-block-or-deeper reorgs have never been observed under normal conditions in Bitcoin's history.
Multi-block reorgs like the March 2026 Foundry event are precisely the scenario confirmation thresholds exist for. Blofin's deposit flow holds affected deposits pending until the winning chain tip is clear, rather than crediting and reversing; this is the same risk-weighted approach exchanges and custodial services apply to protect users from probabilistic-finality risk.
A reorg is not the same as a fork
A reorg is a normal tip adjustment following Bitcoin's existing consensus rules. A Bitcoin fork is a change to the protocol rules themselves. Confusing them leads to unnecessary alarm.
Reorg vs a 51% attack
A natural reorg is a brief, self-resolving chain competition. A 51% attack is a sustained, deliberate attempt to control enough hashrate to rewrite history or double-spend. At Bitcoin's current scale, a sustained 51% attack is practically infeasible.
What happens to your transaction during a reorg?
If a reorg deactivates the block your transaction was in, that transaction leaves the confirmed state and becomes unconfirmed again. In most cases it reconfirms in the new chain within one or two blocks. Three distinct outcomes are possible:
Path A: Reconfirms on the new chain (most common): Your transaction is still valid. It returns to the mempool and miners include it in an upcoming block on the winning branch. Your confirmation count resets to 1 and rebuilds from there. This happens in the large majority of reorgs.
Path B: Becomes conflicted: A double-spend attempt took advantage of the reorg window. A different transaction spending the same UTXOs was confirmed in the winning chain first. Your original transaction is now invalid; the funds went elsewhere. This requires a deliberate adversarial action; it does not happen accidentally during natural reorgs.
Path C: Drops from mempools: Low-fee transactions may be evicted from some mempools during high congestion periods. The underlying funds are not lost; they remain at the source address. The transaction needs to be rebroadcast, possibly with a higher fee.
For more detail on the UTXO model that governs which transaction "wins" when inputs are contested, see our dedicated guide.
What to check if confirmations suddenly drop
Open a block explorer and search your transaction ID. "In mempool" means it's unconfirmed but valid: wait. "Conflicted" means another transaction spent your inputs first; investigate who sent those funds and where they went. "Not found" means the transaction was dropped; check your wallet's broadcast status and rebroadcast if necessary.
Do not panic if you see 0 confirmations after previously seeing 1 or 2. Check the explorer, not just your wallet software.
How many Bitcoin confirmations do you need? Practical thresholds by scenario
No single number fits every situation. The right threshold depends on the amount at stake, the trust relationship between parties, and the policies of any service you are depositing to.
General guidelines:
Transaction scenario | Suggested threshold | Reasoning |
|---|---|---|
Small peer payment, trusted counterparty (<$100) | 0–1 | Reversal risk negligible; counterparty has no economic incentive to attempt it |
Small online purchase, no recurring relationship (<$500) | 1–3 | One block provides initial security; 1-block reorg risk is low |
Mid-value transfer ($500–$10,000) | 3–6 | Covers virtually all natural reorg risk; standard exchange range |
Large transfer ($10,000–$100,000) | 6 | Below 0.1% reversal probability against 10% hash power |
Very high value (>$100,000) or irreversible goods | 6–60 | Extra depth proportional to reversal incentive |
Why exchanges require 3 to 6 confirmations
An exchange credits tradeable account value before the deposit is mathematically irreversible. If a reorg or double-spend attempt succeeded against a 1-confirmation deposit, the exchange absorbs the loss. Higher confirmation thresholds are risk management, not bureaucracy. On the operations side, confirmation thresholds are one of the most carefully calibrated parameters in exchange deposit engineering, because setting them too low exposes the platform to reorg risk while setting them too high creates friction that slows down legitimate users.
BloFin's deposit engineering applies confirmation thresholds weighted against reorg risk at the deposit value: standard retail deposits clear after a small number of confirmations, while larger transfers get proportionally greater depth. The exact threshold appears on the deposit page when you initiate a transfer. For a step-by-step walkthrough of moving BTC off an exchange, see our Bitcoin withdrawal guide.
0-confirmation acceptance
Accepting 0-conf carries real risk with unknown counterparties. It can work between parties with an existing trust relationship, but any merchant or service accepting 0-conf for goods they cannot recall should understand they are extending credit, not receiving final payment.
On-chain vs Lightning
The Lightning Network provides effectively instant settlement for payments routed through open channels, using cryptographic security guarantees rather than confirmation depth. If your use case requires sub-minute finality, Lightning is worth exploring separately. This guide addresses on-chain confirmations.
Why confirmations can take longer: Mempool, fees, and mining incentives
A transaction sitting unconfirmed for an hour is almost always a fee issue, not a problem with your transaction's validity. Understanding how the mempool works explains why.
Every broadcast Bitcoin transaction waits in the mempool, a shared holding area across the network's nodes and miners. Miners constructing a new block select transactions from the mempool to maximize fee revenue within the block's weight limit. A transaction paying 1 satoshi per virtual byte (sat/vB) will wait behind every transaction paying 5, 10, or 50 sat/vB. During periods of high demand (inscription surges, post-halving speculation, large macro events), the mempool can hold hundreds of thousands of transactions, and only the highest-paying ones move.
What fee estimates actually mean: When your wallet shows "confirms in ~10 minutes," it is an estimate based on current mempool conditions. That estimate assumes conditions stay constant until your transaction is mined, which may not hold. A surge in activity after you broadcast can push your transaction further back. Fee estimates are probabilistic, not scheduled.
Block time adds uncertainty: Even with a competitive fee, you may wait longer than 10 minutes simply due to variance. There is roughly a 5% chance that no block arrives within 30 minutes, even at normal difficulty. Bitcoin's block discovery follows a memoryless random process.
The sat/vB rate and transaction size: Fees are priced per virtual byte of transaction data, not per bitcoin sent. A typical native SegWit transaction (1 input, 2 outputs) is about 141 virtual bytes. At 10 sat/vB, that transaction costs 1,410 satoshis (~$1.14 at May 2026 prices). Larger transactions with more inputs cost proportionally more. For a full breakdown of fee mechanics, see how Bitcoin transactions work and our guide on satoshis and fee denominations.
What to do if your transaction is stuck
You cannot cancel a broadcast Bitcoin transaction, but you have two legitimate tools to unstick it: Replace-by-Fee (RBF) and Child-Pays-For-Parent (CPFP). For a full technical breakdown of both methods, see our dedicated stuck transaction guide and the RBF and CPFP options compared.
Replace-by-Fee (RBF): If your original transaction signaled RBF (most modern wallets do this by default), you can broadcast a replacement transaction spending the same inputs with a higher fee. Miners prefer the higher fee version. The original transaction is effectively displaced.
Requirements: your wallet must support RBF replacement; the original must have signaled RBF opt-in (sequence number below 0xffffffff-1).
Child-Pays-For-Parent (CPFP): You (or the recipient) create a new transaction that spends an output from the stuck transaction and includes a high enough fee to make the combined fee rate attractive to miners. Miners have an incentive to confirm both together.
Requirements: you or the recipient must control an unspent output from the stuck transaction.
When waiting is the right call: If the stuck transaction is small, if you are not in a hurry, and if you do not fully understand RBF or CPFP mechanics, waiting costs nothing except time. Mempool congestion typically clears within hours to days. The transaction will confirm.
Scam warning: Services advertising "transaction accelerators" that charge fees, require your private key, or promise guaranteed outcomes are scams or privacy risks. Legitimate acceleration only happens through RBF, CPFP, or a mining pool's voluntary accelerator service; even pool accelerators offer no guarantees.
Common misconceptions about Bitcoin confirmations
"6 confirmations means the transaction is final."
It means reversal risk is very low against rational economic actors under current hashrate assumptions. It does not mean physically impossible. For high-value transactions, 6 confirmations is a practical standard; for very high-value transactions, more depth is appropriate.
"Reorgs happen every 1-2 weeks."
Per actual node data (learnmeabitcoin.com), single-block reorgs occur roughly once every 45 days. The 1-2-week figure overstates frequency significantly.
"If my transaction disappears, my bitcoin is lost."
A dropped transaction does not destroy funds. The bitcoin stays at the source address. The transaction broadcast simply failed to propagate or was evicted from mempools. Rebroadcast with an adequate fee.
"0-conf is always dangerous."
For very small amounts between trusted parties, 0-conf is practical. The risk scales with amount and with the counterparty's ability and motivation to attempt double-spending.
"Faster confirmation = more secure."
Speed and security are separate. A transaction confirming in the next block (fast) has the same 1-confirmation security as one that took 3 hours to confirm in a block (slow). What matters is the depth of confirmations, not how fast the first one arrived.
Frequently asked questions
What is a Bitcoin confirmation in plain terms?
A confirmation is one block added to the blockchain after the block containing your transaction. When your transaction is first included in a block, it has 1 confirmation. Each subsequent block added to the chain adds one more. Six confirmations means five blocks have been added on top of your transaction's block, making reversal extremely unlikely against any economically rational actor.
What does 0 confirmations mean?
Your transaction has been broadcast to the network and appears in the mempool, Bitcoin's holding area for unconfirmed transactions across nodes worldwide. It has not yet been included in any block. Merchants and exchanges almost always require at least 1 confirmation before treating a payment as received.
Can Bitcoin confirmations go down?
Yes, during a chain reorganization. If the block containing your transaction becomes stale because a competing branch accumulates more proof of work, your confirmation count drops, sometimes to 0. In most cases, the transaction reconfirms within a block or two on the new chain. An actual reversal requires deliberate double-spending, not just a natural reorg.
Why do exchanges require more confirmations than peer payments?
Exchanges credit your account with tradeable value before the deposit is mathematically irreversible. If a reorg-assisted double-spend succeeded against a 1-confirmation deposit, the exchange loses the funds. Higher thresholds (typically 3-6 for BTC) protect the exchange and its users from this operational risk.
What is the difference between a reorg and a fork?
A reorg is a normal chain tip adjustment: two valid blocks compete briefly, one wins, and the network updates all nodes to the longer chain with no rule changes involved. A fork is a change to the protocol rules: a soft fork adds or tightens rules (backward-compatible); a hard fork changes rules in a way that old nodes reject. The March 2026 two-block reorg at height 941,880 was a reorg, not a fork; the network resolved it in minutes with zero protocol changes.
How do I check my transaction's confirmation count?
Use a block explorer: paste your transaction ID (txid) from your wallet into the search box. The explorer shows the block number your transaction was included in, how many blocks have been added since, and whether your block is on the current best chain. Multiple explorers (mempool.space, blockstream.info, blockchain.com) cross-check each other; if all three agree on confirmation count, that is authoritative.
What is the right number of confirmations for a $10,000 Bitcoin transfer?
6 confirmations is the standard recommendation for transfers in this range, and it is the threshold most professional services use. At Bitcoin's May 2026 hashrate (~1 ZH/s), the economic cost of assembling enough hash power to reverse a 6-confirmation transaction vastly exceeds the transaction value. For amounts approaching $100,000 or above, 12-20 confirmations provides meaningful additional assurance.
Why do some transactions wait hours before getting their first confirmation?
The transaction is waiting in the mempool because its fee rate is lower than what miners are currently willing to include. During congestion, miners fill blocks with the highest-fee transactions first. A transaction at 1 sat/vB may wait hours or days while transactions at 20 sat/vB confirm in minutes. If you need faster confirmation, use RBF to replace with a higher fee, or check your wallet's fee estimation settings for next-block priority.
Does waiting for more confirmations mean Bitcoin is slow?
The 10-minute average block time is a design parameter; Bitcoin prioritizes security and decentralization over speed. The confirmation wait is the cost of having a settlement system that does not require trusting any bank, payment processor, or government. Applications needing faster settlement use the Lightning Network for off-chain payments that settle on-chain periodically.
Researched and written by the BloFin Academy editorial team with AI-assisted drafting. All facts independently verified.
Disclaimer: This content is for educational purposes only and does not constitute financial, investment, legal, or tax advice. Crypto assets are highly volatile and carry significant risk of loss. Always verify local regulations and consult a qualified professional before making financial decisions.