Start with the result you need to verify

A transaction receipt tells you whether the execution succeeded or reverted and which block includes it. A block’s finality answers a different operational question: whether Ethereum’s consensus has finalized the history containing that block. A reverted transaction can be part of finalized history, and its execution result remains a revert.

Follow the checkpoints

Ethereum groups slots into epochs. Validators attest to blocks and vote on links between epoch checkpoints. A link supported by at least two-thirds of the active stake can justify a checkpoint under the protocol rules. Finalization follows when the checkpoint relationships meet the finality rules. The ancestors of the finalized checkpoint are covered by that finality.

Expect different labels near the chain head

An app’s confirmation count is its chosen measure of how far a block sits behind the head. A justified checkpoint has already received a supermajority link, while finalized gives the stronger protocol guarantee. Under Ethereum’s security assumptions, conflicting finality would imply slashable behavior by at least a third of the stake. Finality can also stall while blocks continue to appear.

Compare the network and time of the lookup

If a provider exposes the finalized block tag, compare its latest finalized checkpoint with the block containing your transaction. Verify that the provider is on the expected network and has caught up. A bridge or exchange may impose its own settlement steps even after Ethereum has finalized the underlying L1 transaction.

Sources

  1. Ethereum.org · Gasper
  2. Ethereum.org · Proof-of-stake

Prepared with AI assistance. This guide explains protocol behavior for educational use.

Editorial policy (Chinese)