Confirmation Time

Confirmation time is the interval between broadcasting a Bitcoin transaction and a miner including it in a block, giving it its first confirmation. Bitcoin targets one block roughly every ten minutes, so a well-fee'd transaction broadcast just after a block is found may confirm within minutes, while one broadcast moments before the next block often waits a full extra round. Confirmation time is where most newcomers first feel Bitcoin's design trade-offs in their own hands: settlement is probabilistic, market-priced, and utterly indifferent to how urgently you personally need it.

The number is worth watching because it encodes the state of the whole system in a single figure: how full blocks are, how aggressive current fee competition is, and how recent hashrate swings have skewed block cadence. Most of the frustration people feel about it comes from a category error — treating Bitcoin like a payments app with a service-level agreement, when it is a settlement system running a continuous open auction for scarce block space. Once you internalize that framing, confirmation time stops being mysterious: it is simply the market-clearing delay for the priority you chose to pay for, plus the irreducible randomness of proof-of-work.

What drives it: the fee market

The dominant factor is your fee rate — satoshis per virtual byte — relative to everything else waiting in the mempool. Block space is scarce and miners assemble candidate blocks to maximize fee revenue, selecting the highest-paying transactions first. Your transaction is therefore in a continuous blind auction: when the mempool is congested, a low-fee transaction can wait hours or days, and when demand is slack, even a minimal fee may confirm in the next block. The mempool's depth at your fee rate — how many paying bytes are queued ahead of you — is the single most informative thing you can look at before broadcasting.

The randomness on top

Even at a winning fee rate, timing is genuinely random. Block discovery is a Poisson process: each hash attempt is an independent lottery ticket, so intervals between blocks vary enormously around the ten-minute average — two blocks in a minute, then a forty-five-minute drought, all perfectly normal. The ten minutes is an average enforced by the difficulty adjustment, not a schedule; when network hashrate grows faster than difficulty catches up, blocks run slightly fast, and after abrupt hashrate drops they run slow until the next adjustment. None of this can be bought off with fees — a high fee wins you the next block, whenever the network happens to find it.

Estimating, and rescuing, a transaction

Fee estimation tools and mempool explorers translate current congestion into a prediction — "this fee rate should confirm within N blocks" — and checking one before broadcast is the single best habit for avoiding both overpayment and stuck payments. If a transaction is already stuck, two rescue paths exist: Replace-by-Fee lets the sender rebroadcast the same spend with a higher fee, while Child-Pays-for-Parent lets whoever controls an output attach a high-fee child transaction that makes the pair attractive to mine together. Wallets increasingly automate both; see also unconfirmed transaction and transaction accelerator for the waiting state and the service-based escape hatch.

How many confirmations is "confirmed"?

The first confirmation is a milestone, not a finish line. Each additional block buried on top makes reversal exponentially harder, because an attacker would have to redo all that proof-of-work faster than the honest network extends it. Convention scales caution to value: small retail amounts are often treated as settled at one confirmation, while exchanges commonly wait for several — six remains the traditional benchmark for high-value settlement. For a miner, this same maturation logic applies with force: freshly minted coinbase rewards cannot be spent until coinbase maturity, one hundred blocks deep. Confirmation time is Bitcoin's honesty made visible — settlement assurance is earned in work, block by block, not declared.