01

Your wallet says "sent," so why hasn't it arrived?

A wallet usually shows "sent" within seconds, yet the receiving exchange may take minutes, sometimes more than an hour, to credit the deposit. In the meantime the transaction is moving through several stages, each with a different chance of being reversed.

This guide follows a transaction from broadcast to inclusion in a block to the point where it is effectively irreversible. It compares how Bitcoin and Ethereum approach finality, explains why exchanges set their own deposit thresholds, and ends with a checklist for sending.

02

The stages of a transaction

A signed transaction is first broadcast to nodes and waits in the mempool. At this stage it is not in a block, so a low fee can leave it waiting for a long time or eventually dropped. Ethereum.org's documentation on transactions describes this pending state before inclusion.

When a block producer includes it, the transaction is in a block. Each new block built on top adds a confirmation and makes reversal harder, because more blocks would have to be redone. Being included is still not the same thing as being final.

What each status means (Ethereum, typical conditions)
StatusRoughly whenWhat can still happen
Pending (mempool)Right after signingDelay, replacement with a higher fee, being dropped
Included in a blockUsually within seconds to a minuteRarely, a short reorg can change ordering
Several confirmationsA few minutesThe chance of reversal keeps shrinking
FinalizedAbout two epochs, around 13 minutesReversal would require massive stake losses

Times are approximate and depend on network conditions. Bitcoin has no separate finalized stage; reversal simply becomes harder as confirmations accumulate.

03

Bitcoin: probabilistic finality through confirmations

Bitcoin uses proof of work, and nodes follow the chain with the most accumulated work. The Bitcoin Developer Guide explains that each additional block increases the work needed to change the transactions beneath it. Blocks arrive about every ten minutes on average, so more confirmations also means more waiting.

Finality on Bitcoin is therefore probabilistic. One confirmation is enough for most everyday transactions, but recipients of large amounts typically wait for several. Many services use a fixed number of confirmations as their rule of thumb for that reason. For a hypothetical illustration, an exchange requiring three confirmations for Bitcoin deposits implies an average wait of around 30 minutes, though block intervals vary.

04

Ethereum: finality by checkpoints

Ethereum's proof of stake places checkpoints at the start of each 32-slot epoch, about 6.4 minutes. When enough validators vote, checkpoints are justified and then finalized. Ethereum.org's FAQ explains that a block becomes a permanent part of the canonical chain only after receiving votes from a supermajority of validators. Under normal conditions this takes about two epochs, roughly 13 minutes.

Reverting a finalized block would require an attacker to accept the loss of a large share of all staked ETH, which makes it economically prohibitive. Finality can occasionally be delayed when validator participation drops, and exchanges may slow deposits while that lasts.

05

Why exchanges set their own deposit rules

Exchanges decide, network by network, how many confirmations or whether finality is required before crediting a deposit. If a deposit were reversed after the customer had already withdrawn funds, the exchange would bear the loss. Thresholds vary between exchanges, and they may be raised or deposits paused when a network has problems.

That is the source of the gap between your wallet's "sent" and the exchange's "credited." Looking up the transaction hash in a block explorer shows its current confirmations or finality status, which you can compare with the exchange's stated requirement.

06

Failed versus pending

On Ethereum, a transaction can be included in a block and still fail. If a smart contract's conditions are not met or the gas limit is too low, it is recorded as failed and the gas already used is not refunded. Pending and failed transactions call for different responses, so check the status first.

A transaction stuck as pending can often be replaced by sending a new one with the same nonce and a higher fee. A failed transaction has to be fixed and sent again as a new transaction.

07

A sending checklist

Use these steps for large transfers or when a deposit is slow to appear.

  1. Check the receiving exchange's deposit requirement (confirmations or finality) for that network before sending.
  2. After sending, look up the transaction hash in a block explorer and note whether it is pending, included, or failed.
  3. If included, compare its confirmations or finality status with the exchange's requirement to estimate the remaining wait.
  4. If it failed, read the error reason; if it is pending, decide whether to replace it with a higher fee.
  5. Check the exchange's announcements for deposit delays or maintenance on that network.
08

What finality does not guarantee

Finality means the blockchain record will not be reversed. It does not mean a mistaken transfer can be recovered; if you used the wrong address or an unsupported network, finality makes reversal even less possible.

The stages and times here describe typical conditions and can change with network upgrades or unusual events. When sending, rely on each network's official documentation and the exchange's latest notices, noting when each was last updated.