How long does a crypto transfer take?

The two clocks

The first clock is the network. Your transaction waits in the mempool until it is included in a block, which depends on the fee you offered relative to what is being accepted. On Ethereum, blocks come roughly every twelve seconds; a competitively priced transaction is usually included almost immediately.

The second clock belongs to the receiving platform. Exchanges require a number of confirmations before crediting a deposit, and they set that number per asset for their own risk reasons. Kraken states plainly that deposits must receive a number of confirmations before funds are credited, and gives Bitcoin as an example: four confirmations, roughly forty minutes at an average ten-minute block time.

A transaction can therefore be final on the network and still, correctly, uncredited in an account.

What actually makes a transfer slow

An underpriced fee. If you offered less than the network is currently accepting, the transaction waits until conditions change. This is the main cause of a genuinely stuck send.

A high confirmation requirement. Nothing is wrong; the destination is waiting by design.

Block time variance. Kraken notes that a single Bitcoin block can take thirty or sixty minutes even though the average is ten. Averages are averages.

Platform review. A deposit or withdrawal can be held for compliance or security checks that have nothing to do with the network.

A different problem entirely. Wrong network, missing memo, unsupported token version or an amount below the deposit minimum. These do not resolve by waiting.

How to check where it is

Start with the transaction hash. Search it on the block explorer for the network you used, and read the status. A successful transaction shows the sending address, the receiving address, the amount and the fee paid; a pending one is still waiting; a failed one executed and did not succeed.

If the explorer shows success and the destination is an exchange, the transaction is done and the account is waiting on confirmations or review. If the explorer shows the transaction went to a different address or a different network than you intended, the delay is not the issue — see sent on the wrong network.

Our guide to reading a block explorer walks through the fields.

Rough expectations, and why they are rough

As a working expectation: a transfer between two self-custody wallets on a layer 2 is usually a matter of seconds once included; on Ethereum mainnet, a minute or two for inclusion and around thirteen minutes for finalisation; a deposit to an exchange, the network time plus that platform’s confirmation requirement and any review.

Canonical withdrawals from an optimistic rollup back to Ethereum are the outlier: a challenge period measured in days, by design, not by congestion.

These are shapes, not promises. Every platform publishes its own requirements and every network has busy periods.

When waiting stops being the answer

If the explorer shows the transaction is still pending and you can see that fees have risen since you sent, the transaction may need replacing rather than waiting. Most wallets offer a speed-up or cancel action while a transaction is pending — see speeding up or cancelling.

If the explorer shows success but nothing arrives after the destination’s stated confirmation requirement has clearly passed, contact the platform through its official support route with the transaction hash. Never through a number or link someone sent you: recovery and support impersonation are a standard scam, covered in support impersonation scams.