Six Bitcoin confirmations are often translated into “about an hour”. That is an expectation based on an average block interval, not a countdown attached to your payment. The confirmation number measures how far a transaction’s block sits inside the current chain. To interpret it, separate three events: broadcasting the payment, its inclusion in a block, and the arrival of subsequent blocks.
| What you need to know |
|---|
| The block containing a Bitcoin transaction gives it its first confirmation. |
| Later blocks increase its confirmation count as the active chain grows. |
| The average block interval does not guarantee a time for any individual payment. |
| A blockchain confirmation count and a service's account-credit decision are separate checks. |
Count the containing block too
Imagine a transaction included at block height 900,000. If that block is currently the chain tip, the transaction has one confirmation. When the tip reaches 900,001, it has two; at 900,002, it has three. These invented heights illustrate counting. They are not a report of the current Bitcoin chain.
For a transaction in the active chain, the worked calculation is the current tip height minus its inclusion height, plus one. The extra one counts the containing block itself. Waiting for six confirmations means waiting until that block has five further blocks above it, rather than waiting for six new blocks after inclusion.
Bitcoin Core 30.0’s transaction lookup documentation distinguishes the containing block’s hash from the confirmation field and also exposes whether a specified block belongs to the active chain. This distinction matters when comparing a saved transaction record with an updated view of the chain. A transaction identifier lets you locate the payment; it does not by itself establish how deep its block is now.
The waiting period has two parts
A broadcast transaction still awaiting its first inclusion has no confirmed block from which to count depth. That initial wait is different from the wait for further blocks after inclusion. A clock started when you pressed send combines both periods, so dividing elapsed minutes by ten cannot tell you the payment’s confirmation count.
The Bitcoin.org guidance on unconfirmed transactions explains that block discovery is probabilistic. Its discussion of confirmations treats additional blocks as increasing resistance to reversal, while giving an approximate average interval of ten minutes. An individual block can arrive earlier or later. The same guidance notes that a fee below what the network prioritizes can prolong the first-confirmation wait.
Use the transaction’s actual status to check progress. Match its transaction identifier, recipient output and amount to the payment you intended, then look at inclusion and confirmations. If two views disagree, check when they were updated and whether they are displaying the same transaction. An old screenshot is a record of an earlier observation, not a current counter.
A service receiving the payment can apply its own crediting process. Treat the confirmation figure as blockchain information and check the service’s current deposit instructions separately. A high counter does not demonstrate that a provider has matched the payment to your account or completed its own checks. This article gives no universal service threshold or promised credit time.
Neither the worked heights nor the hourglass records a live payment. The authentic Bitcoin symbol was added to the conceptual image separately. Source check: 12 October 2026, 00:30 CEST.
