Crypto basics

Bitcoin confirmed, but your deposit is still pending?

Learn to count confirmations and separate the blockchain record from exchange account credit, with a three-block example.
Three interlocking blue ceramic blocks beside a separate gateway in a conceptual illustration.
Network confirmation and account credit are separate steps — conceptual illustrationCoinFom · AI-generated illustration with OpenAI

At a glance

A confirmation records a transaction’s inclusion in a block; later blocks increase the count. Crediting an exchange account is a separate step subject to deposit requirements. Neither a confirmed label nor a time estimate guarantees that the balance is already available.

On this page

A Bitcoin explorer shows confirmations, but your exchange balance has not changed. Those screens answer different questions: one describes a transaction on the blockchain; the other describes credit in a particular account.

This article covers on-chain Bitcoin deposits, not Lightning payments, wrapped BTC or internal transfers between exchange accounts. It explains how to read the confirmation count before deciding what to investigate.

Count blocks, not repeated payments

A transaction receives its first confirmation when it is included in a block. Later blocks built on that block add confirmations; they do not send the payment again. The Bitcoin developer guide describes this increasing depth in the chain.

For a transaction still included in the active chain, count from its inclusion block through the current tip, including both ends. A chain reorganization can change that observation, so it is not an unconditional promise of finality.

A three-block example

Imagine a transaction included at height 900,000. These are deliberately hypothetical observations, not a report about a real transaction.

Current tipCalculationConfirmations
900,000900,000 − 900,000 + 11
900,001900,001 − 900,000 + 12
900,002900,002 − 900,000 + 13
One inclusion block and two later blocks produce three confirmations in a hypothetical active chain.
Hypothetical block heights, without timestamps or any particular exchange’s threshold. CoinFom · Original diagram and calculation

The plus one matters: simply subtracting the heights would wrongly give zero at first inclusion. Three confirmations here mean the original block plus two successors, not three separate deposits. The count is not the BTC amount and does not tell you which customer account an exchange has credited.

Ten minutes is not a countdown

Bitcoin targets roughly ten minutes per block on average. Individual intervals vary, and a transaction can also wait before inclusion. Multiplying a deposit threshold by ten therefore does not produce a guaranteed arrival time. Bitcoin.org explains the timing uncertainty.

In our example, the heights let us calculate three confirmations. They do not give us the elapsed minutes: we have supplied no timestamps. Keep that distinction when a progress screen tempts you to estimate an exact deadline.

The exchange has another decision to make

Coinbase Exchange describes deposits staying pending until its required network confirmations are reached. That is a platform rule, not a universal Bitcoin threshold.

Other requirements can matter too. Binance lists unsupported networks, incorrect destination details, deposit minimums and wallet maintenance among reasons a deposit may not appear. Its deposit troubleshooting page is an example of platform-specific guidance, not proof that the same rules apply to your account elsewhere.

Use the receiving exchange’s current BTC deposit instructions for the Bitcoin network. Check the threshold, minimum and service notices there. A green confirmation indicator alone does not establish that every receiving requirement was met.

Make the next check specific

Record the transaction ID, receiving address, asset, network, amount and time privately. Then separate the evidence:

  • No transaction ID available: inspect the sender’s withdrawal record before assuming the transfer reached the network.
  • Zero confirmations: investigate inclusion status; this is different from a confirmed deposit awaiting account credit.
  • Some confirmations, below the receiving requirement: compare the live count with the current deposit instructions, without promising a completion time.
  • Requirement met but balance absent: review the destination details and service notices, then contact the receiving platform through its verified support channel with the transaction record.

This is an investigation sequence, not a diagnosis or a recovery guarantee. Avoid sending another payment simply to resolve an unexplained status. Before a future transfer, use our transfer checklist; for suspicious support messages, see account security.

For a different network and routing problem, see XRP destination tags and account credit. That article explains customer identification, not Bitcoin confirmation thresholds.

CoinFom editorial note: researched and drafted with AI assistance, including an AI source and calculation review. No deposit was performed for this article. The example and diagram are original educational illustrations. Sources checked September 25, 2026; platform instructions can change. See About CoinFom, our editorial and affiliate disclosure, or send a correction. CoinFom may earn referral commissions elsewhere on this site; this article contains no signup link.

All articles ↗