Understand blockchain confirmations, mempool delays, and why an exchange waits before crediting an incoming transaction.
Why this matters
Broadcasting a transaction and receiving it safely are not the same event. First the network sees the transfer, then a validator or miner includes it in a block, and later blocks increase confidence that the payment is final. Exchange services therefore wait for a network-specific number of confirmations before processing the payout.
Confirmation speed depends on block time, network congestion, the fee selected by the sender and the risk policy for that asset. A visible transaction hash proves that a transfer was created, but it may still be pending, replaced or insufficiently confirmed.
Practical checklist
- Copy the transaction hash from the sending wallet and open a trusted explorer for the correct network.
- Confirm that status, destination address, asset and amount match the order.
- Check whether the transaction is pending or already included in a block.
- Compare its confirmation count with the requirement shown on the order page.
- Contact support with the order ID and hash if the requirement is met but the status does not update.
Common mistakes
Refreshing the page cannot accelerate a blockchain. Sending a second payment without support instructions may create an overpayment, while using an explorer for the wrong network can make a valid transfer appear missing. Never share a seed phrase or private key for status verification.
Bottom line
Confirmations protect both sides from unsettled payments. Track the correct transaction hash and network, then distinguish a normal confirmation wait from a payout issue that requires support.