Look up the hash on the correct network. Check inclusion, confirmations and any explicit finality status. Wait for the receiving service’s stated threshold before treating payment as received.

Not yet included

Included with later blocks

Consensus-specific status
Broadcast and inclusion
A submitted transaction may remain pending, be replaced or fail. Inclusion in a block is a milestone, not necessarily acceptance by the recipient.
Confirmations and finality
More blocks generally reduce reorganization risk. Some networks provide explicit finality; do not copy a fixed confirmation count between networks.
Recipient rules
An exchange or merchant may wait longer according to asset, network, amount and risk controls. Check its requirements before sending.
Proof of receipt
Keep the hash, network, address, asset and time. A confirmed transfer to the wrong address or network does not guarantee account credit.
Decide when to deliver goods
A broadcast transaction is not necessarily included; an included block may still reorganize depending on the network. Set a confirmation rule suited to the value and finality mechanism.
- Check status on the exact network.
- Distinguish technical finality from a provider’s internal credit.
Practical case: decision and limits
An included transaction may need more confirmations before a service credits it. Bitcoin confirmations are probabilistic; more blocks reduce risk without a universal absolute guarantee. Ethereum distinguishes inclusion from finalized checkpoints. Do not use one confirmation count for every network or amount; check recipient policy and network state before diagnosing an unusual delay.
A concrete verification
Ask the recipient’s threshold: on-chain confirmation and internal account credit remain different events.
Hypothetical case: visible inclusion, no provider credit
An Ethereum transaction appears in a block with successful execution, but a provider has not credited the account. Execution status, inclusion, finality and internal credit are distinct stages. Compare network, contract, beneficiary and documented requirements before concluding failure or sending the amount again. Network finality does not establish correct recognition in the provider’s internal system.
- Keep hash, block and observed status with the check time.
- Find the recipient’s required confirmations or finality state in its documentation.
- Give official support useful public references; screenshots and “acceleration” promises do not replace diagnosis.
Read Ethereum’s safe and finalized block states
On Ethereum layer 1, node interfaces can distinguish latest, safe and finalized. For a payment, record the hash and number of the block containing it. If the service shows a newer finalized block, also check that the payment’s block belongs to the canonical chain, especially after an explorer reports a reorganization. Layer 2 networks and platform deposit credits follow their own steps.
Checks to make
| Item | Check |
|---|---|
| Pending | Not yet included |
| Confirmed | Included with later blocks |
| Finalized | Consensus-specific status |
Frequently asked questions
Is one confirmation always enough?
No. The threshold depends on network and recipient.
Does a hash prove exchange credit?
No. It proves an onchain event, not internal processing.
Can a failed Ethereum transaction be confirmed?
Yes. An included transaction can have a failure receipt. Failed-call state changes revert, but consumed gas is paid and the nonce used. Check execution status before concluding the recipient received the asset.
Verifiable sources
Ethereum.org: Transactions
Ethereum.org: Proof of stake and finalityBitcoin Developer Guide: Block chain
Ethereum.org: Gasper and finality
Ethereum.org: Block status in JSON-RPC
Independent educational content reviewed against primary documentation. No personalized recommendation or promise of returns. Updated November 15, 2026
Prepare and continue reading

Useful background
- Consensus, mining and staking: understand who validates what
Consensus is the set of rules that lets independent nodes choose a common history. Proof of Work commits computation and energy; Proof of Stake commits assets and applies penalties. Neither mechanism removes centralization, outage or governance risks.
- How to read a transaction in a block explorer
Copy the transaction hash from your wallet, open a trusted explorer for the correct network, then compare status, addresses, asset, amount, fees and confirmations. Never enter a recovery phrase.

Continue to the next step
- Layer 2 and bridges: move faster without losing track of risk
A Layer 2 executes or batches operations, then publishes data or proofs to a base layer. A bridge moves or represents an asset between systems. Each step adds contracts, operators, delays and security assumptions that need checking.
- Sending cryptocurrency: check the asset, network and address
Before signing, ask the recipient to confirm the asset, network and full address. Check any extra destination fields, fees and amount received. For a new destination, start with a small test and wait for receipt.




