How long a deposit takes
The statement: a deposit takes about twenty minutes. Sometimes it does. The number is a memory of one transaction on one day, repeated until it became a rule.
Bucket: DEPENDS
It depends on the fee you attached, how busy the network is, how many confirmations the receiver waits for, and how quickly the receiver notices a confirmed transaction. Four things, and they multiply rather than add.
The variables
| Variable | Direction | Can you see it |
|---|---|---|
| Fee you attached | Higher fee, sooner included | Yes, before you send |
| Network congestion | Busier, longer wait at any fee | Yes, on a public explorer |
| Confirmations required | More required, longer wait | Usually stated on the deposit page |
| Block timing luck | Random, can add a whole block | No |
| Crediting delay at the receiver | Adds an unknown tail | No |
Which ones you control
Exactly one. The fee, and only before you press send. After that you have no levers at all, and everything that happens is somebody else's scheduling decision.
This is why the useful moment is earlier than people think. Deciding to wait for a cheap fee is a decision to wait longer, made at the point of sending. It cannot be revisited by refreshing a page later.
The invisible tail
The last variable is the one that ruins estimates. A market credits deposits when its own systems notice, and that noticing is a background job with its own schedule. A transaction can be confirmed on the chain and uncredited in your balance for a while, and from outside that looks identical to a transaction that has not confirmed.
Checking the transaction on a public explorer separates those two cases. Confirmed on chain and not credited is a waiting problem. Not confirmed is a fee problem. They call for different amounts of patience and no amount of refreshing distinguishes them.
What people get wrong
They compare their wait to somebody else's and conclude something is broken. The comparison is meaningless unless both transactions paid similar fees at similar congestion for a receiver with the same policy. Almost never true.
They also resend. This is the expensive mistake. A second transaction does not cancel the first, and now two payments exist, both final. See why nothing gets recalled.
Why the twenty minute figure sticks
Because it was true once and it is short enough to remember. Numbers that fit in a sentence outlive the conditions that produced them. Nobody repeats the version with four clauses attached, so the bare number travels and the conditions do not.
The same thing happens with three confirmations, two percent and twenty four hours. Each started as somebody's real experience and got stripped down to a figure that no longer refers to anything.
The honest answer
If you paid a competitive fee and the network is quiet, inclusion in the next block or two is ordinary. If you paid low during a busy period, hours is ordinary and days is possible. If it is confirmed and not credited, you are waiting on somebody's job queue and nobody outside can tell you how long that is.
That is our judgement based on how these systems are built, not a measurement, and we are not measuring anything.
Questions people actually ask
My deposit has not shown up after an hour, is it lost?
Check the transaction on a public explorer. Confirmed and uncredited is a waiting problem. Unconfirmed is a fee problem. Neither is a lost payment.
Can I speed up a transaction I already sent?
Depending on the coin and whether replacement was signalled, sometimes. Treat it as unavailable unless you already know how.