What is a blockchain confirmation, and why does your transfer have to wait for it?

A transfer shows up in the explorer with one confirmation, yet the receiving side still says “pending.” Nothing is wrong. The network has recorded the transaction, but the receiving side hasn’t yet counted enough blocks to treat it as settled.

That waiting period is what a blockchain confirmation count measures. Here’s what it counts, why one block isn’t always treated as enough, and how long it usually takes.

What a confirmation actually counts

When a transaction is broadcast, it first waits to be picked up and included in a block. Once it’s added to a block, it receives its first confirmation. Each block added on top of that one counts as another confirmation. A transaction that hasn’t been included in a block yet typically shows as pending, with zero confirmations.

So the number isn’t a rating of the transaction. It’s a count of how many blocks have been built after it, which is why it only ever goes up as the chain grows.

Why one block isn’t always enough

On proof of work networks such as Bitcoin, two miners can occasionally find a block at nearly the same time, creating two temporary versions of the chain. The network ends up following one of them, and the blocks on the other are discarded. Transactions that were in a discarded block go back to the waiting pool and must be confirmed again. This is called a reorganization, and it’s a rare event.

Each extra block on top makes reversing a transaction harder, so the risk falls as the count rises, though on proof-of-work chains it never quite reaches zero. The main concern is double-spending, where a sender tries to spend the same funds twice in conflicting transactions. Waiting for more confirmations protects the person receiving the funds.

How many confirmations are enough?

There is no universal number. For Bitcoin, waiting for around six confirmations is a commonly cited convention, and with a target of roughly one block every ten minutes, that’s about an hour. It’s a convention, not a protocol rule, and some users accept fewer for smaller amounts.

Other networks work differently. Ethereum added finality after moving to proof-of-stake. Validators vote on checkpoints once per epoch, and a block is finalized after about two epochs, roughly 13 minutes, after which reversing it would require destroying a very large share of all staked ETH. Many applications still wait for a fixed number of confirmations instead of full finality. Solana doesn’t count confirmations at all, and uses three statuses, processed, confirmed, and finalized. Wallets and platforms each decide how many confirmations they require before treating funds as available.

Where to see the confirmation count

Paste the transaction hash into the explorer for the network you used. The page typically shows the status, such as pending, success, or failed, along with the confirmation count or an equivalent status. Etherscan, BscScan, Solscan, and Tronscan all work this way, and the details differ slightly between them.

A transfer can be successful on-chain while the receiving wallet or platform still shows it as pending, because each one decides how many confirmations it needs. If a transaction stays unconfirmed for a long time, it’s often because the fee attached was too low for current network conditions, and waiting or using the wallet’s speed-up option, where one exists, is the usual route. Resending the same transfer while the first is still pending can lead to sending it twice.

WEEX Reminder: be patient with confirmations

WEEX reminds users that the wait is part of how the network keeps transfers secure, not a sign that something went wrong. Check the transaction hash on the right explorer before resending, and treat a transaction with zero confirmations as not final, especially before handing over goods or funds in return. Be wary of anyone who pressures you to skip the wait or sends a screenshot as proof, and never share a seed phrase or private key in the process.

Conclusion

A blockchain confirmation counts how many blocks have been added since a transaction was recorded. More confirmations mean it’s harder to reverse, which is why wallets and platforms wait for a set number before treating a transfer as settled. The right number depends on the network, and the explorer will show you where your transfer stands.

FAQ

1. What is a blockchain confirmation?
A confirmation means a transaction has been included in a block. Each additional block added on top counts as another confirmation, so the number grows as the chain grows.

2. Why does a transfer need more than one confirmation?
Recent blocks can occasionally be replaced in a chain reorganization, so each extra block makes a transaction harder to reverse. Waiting for several confirmations lowers the risk of a reversal or double-spend.

3. How many confirmations are needed?
It depends on the network and on the wallet or platform receiving the funds. For Bitcoin, around six is a commonly cited convention, but it isn’t a protocol rule.

4. Is a transaction with zero confirmations safe to rely on?
Not as final. A transaction with zero confirmations hasn’t been included in a block yet, so it can still change or never complete. It’s best treated as pending until it receives confirmations.

5. Do all blockchains count confirmations the same way?
No. Bitcoin and many other chains count blocks, Ethereum also has finality based on validator votes, and Solana uses processed, confirmed, and finalized statuses instead of a count.