Finality: Stronger Chain Evidence Than First Inclusion
First seeing a transaction in a block answers whether it was included in that observed chain. Finality concerns the stronger conditions under which the network treats that history as settled.
Separate the lifecycle states
A pending transaction has not yet supplied an included execution receipt. An included transaction belongs to an observed block. Further chain progress and consensus rules determine how confidently that block belongs to settled history. Ethereum’s Gasper documentation explains finalized checkpoints and the severe consensus-failure conditions involved in reversing finalized history. Do not equate this with a website’s success animation or an arbitrary waiting timer.
Use the relevant network model
A layer-two network can distinguish sequencer inclusion, publication to its settlement chain and finality of that settlement data. Base documents its own transaction-finality stages. These are different questions from how long a particular bridge withdrawal must wait. Avoid copying Ethereum confirmation expectations onto Base or using a bridge’s withdrawal window as a universal description of ordinary wallet-transfer inclusion.
Read counters in context
Suppose an explorer says a transaction has several confirmations. Check how that explorer defines the count and which chain it is displaying. A count of later blocks is useful evidence but not a universal replacement for a protocol’s finalized-state condition. For a service deposit, the receiving service may also apply its own crediting policy. That policy is separate from what the underlying chain reports.
Record the claim you can actually support
A careful report might say included in an identified block at a given observation time, while finality remains unchecked. If finalized evidence is available, record its source and relevant block identity. No fixed completion time is promised here. RunixCoin’s public quote form submits no swap, so obtaining an estimate does not begin a verified onchain finality process. This guide changes no transaction-tracking or execution behavior.
References and verification
Reviewed . Product limits reflect inspected public interface code. These are educational checklists, not reports of tested mainnet transactions; browser behavior and execution were not verified.