Crypto transaction confirmations: pending, confirmed and final

The short answer

A transaction shown as sent is not necessarily final. Its hash, network, block inclusion and the recipient service's confirmation policy must all be checked separately.

Separate sent, pending, confirmed and final

A wallet can display sent as soon as it broadcasts a signed transaction. That does not mean the transaction is already in a block or available to the recipient. On Ethereum, a broadcast transaction normally enters a pool of pending transactions before a validator selects it for inclusion in a block.

After block inclusion, confidence increases as the chain progresses. Ethereum distinguishes later justified and finalized states. A wallet, exchange or merchant can apply an additional crediting policy, so a transaction can be confirmed on-chain while the receiving account still shows a pending deposit.

Use the transaction hash as the primary reference

The transaction hash is the network reference for a submitted transfer. Copy it from the sending wallet or service and inspect it with a block explorer for the correct network. Check the sender, recipient, asset or token contract, amount, fee, block and status rather than relying on a screenshot or a message saying that payment was sent.

A hash that cannot be found may indicate the transaction was never broadcast, was submitted to a different network, or has not reached the explorer being used. Confirm the network first. Never share a seed phrase or private key with anyone who offers to trace or accelerate a transfer.

Why a transfer can remain pending

Block space is limited and transactions compete for inclusion. A low fee during busy conditions can leave a transaction pending longer than expected. Account-based networks can also process transactions from the same address in nonce order, so an earlier pending transaction may delay a later one.

Do not send the same payment again merely because a balance has not updated. First compare the on-chain status with the receiving service's deposit rules, minimum amount, supported token contract and required confirmations. The service may also be carrying out an internal review after the network has confirmed the transfer.

Troubleshoot without creating a second loss

Verify the destination address and network before signing because cryptocurrency payments are typically not reversible. If the address or network is wrong, a block confirmation does not make the intended recipient receive the funds. Contact the sending and receiving services promptly, but treat recovery promises that request another crypto payment as a scam warning sign.

If the on-chain transaction succeeded but the account was not credited, give support the hash, network, asset, amount and time. If it is still pending, use only replacement or cancellation features documented by the wallet provider; these actions are network-specific and are not guaranteed.

• Confirm the exact network before searching the hash.
• Match recipient, asset contract and amount.
• Check the receiver's confirmation and minimum-deposit policy.
• Never disclose a seed phrase or pay a recovery agent.

Practical checklist

• Save the transaction hash and identify the exact network.
• Check block inclusion, status and confirmation depth.
• Compare on-chain status with the recipient's crediting policy.
• Avoid duplicate transfers and never share wallet recovery secrets.