A deposit reaching enough confirmations

The wait, in plain words

A deposit page that says received, or pending, or seen, is telling you the network noticed your transaction. It is not telling you the market will spend it. Those are separate decisions taken by separate parties, and the second one has conditions attached.

This is where watching gets confused with checking. Watching is sitting on the deposit page with the tab open, reloading, reading the same line in a slightly different mood. Checking is opening the page once, later, to see whether the state changed. The first costs you an evening and returns nothing. The second costs a few seconds and returns exactly the same information.

Go and do something else. When you come back the credit will either be there or it will not, and neither outcome was affected by your attention.

Underneath, while nothing moves

When you sent the coins, your wallet handed a signed transaction to the network. It waited in a pool of unconfirmed transactions until whoever was building the next block chose to include it. That inclusion is the acknowledgement, and it is the smallest event in this story.

After inclusion, the only thing that changes is how much work stands behind your transaction. Every further block makes rewriting that stretch of history more expensive for anyone who wanted to. The market picks a depth it is willing to accept and will not credit before it, because crediting early is how a business gets paid with money that later stops existing. The depth is a risk decision on their side. It is not a service level offered to you.

Different assets settle at different rates because they were built to. Chains differ in how often they produce blocks and in how much a single block is worth as evidence, so a market that credits one asset quickly and another slowly is being consistent rather than arbitrary. If a deposit in a different coin cleared faster for you once, that was a property of the coin.

The fee is already fixed. You chose it at broadcast and it buys one thing: attention from whoever assembles the next block. Once your transaction is in a block, the fee has spent its entire usefulness. It cannot buy depth. Wishing it higher does nothing, and while a transaction is still unconfirmed, whether it can be replaced with a better paying version is a property of your wallet and the asset, settled before you pressed send.

Seen

Broadcast and sitting in the pool of unconfirmed transactions. Nothing has been decided about it yet.

Included

A block carries it. This is the acknowledgement, not the credit.

Deep enough

Enough further blocks stand behind it to satisfy whatever depth the market set for that asset.

Credited

The market moves the number. The balance catching up covers why this can still lag the depth itself.

Behaving, and not behaving

A deposit that is behaving looks like nothing at all for most of an evening. The failures look like nothing too, at first, which is why the question that separates them is about the transaction rather than about the page in front of you.

The split is between inclusion and depth. If your transaction is in a block, waiting is the correct move and the only move. If it is not in a block, waiting may still be correct, but you are waiting on a different thing and the depth requirement is not what stands in the way.

Neither case is improved by a ticket written tonight. A ticket asks a person to look at something the software will resolve without them, and it puts you behind everybody whose problem genuinely needs a person. A support ticket is a wait of its own, and opening one early does not make the answer early.

Safe to do meanwhile

Everything below is either useful later or harmless now. None of it speeds up the deposit, because nothing speeds up the deposit.

• Write down the transaction identifierSomewhere outside the browser. It is the only handle you have if this ever needs discussing with anyone.
• Read why this site prints no figuresDepth requirements and settlement rates differ by asset and by market, so a number written here would be wrong for someone.
• Look at the shorter version of this waitThe acknowledgement you have already passed, and why it belongs a band lower than this one.
• Close the deposit tabClose it, do not minimise it. Reopening later takes a moment and it breaks the reloading habit.

What makes it longer

Most of what stretches this wait was decided before you started, which is why the list reads as a set of past choices rather than present mistakes.

• A low fee chosen at broadcast, which delays inclusion. Depth cannot start accumulating until inclusion happens.
• A busy network, where the pool of unconfirmed transactions is long and your fee buys less attention than it would have on a quiet day.
• An asset that settles slowly by design, paired with a market that wants a lot of work standing behind it.
• Sending from a service that batches its withdrawals, so your transaction was not broadcast at the moment you pressed send.
• Reloading the deposit page all evening, which does not lengthen the deposit but reliably lengthens the evening.

What this card is not. This card cannot tell you how deep your particular deposit is, and it does not promise that any deposit clears inside an evening.

Questions people ask about this wait

Does the market see a deposit before it credits it?

Generally yes. The deposit page acknowledging a payment and the balance moving are two separate events, and the gap between them is the depth requirement doing its job.

Can paying more make a deposit confirm faster?

Not after the fact. A fee buys inclusion in a block, not the blocks that come after it, so once the transaction is included the fee has no further effect on anything.