in a masterchain block — a masterchain block has sealed the shard block holding the credit on the recipient's jetton wallet; the docs call this final (done and final are the same level here)
slowest
in a shardchain block 2.4 s→ in a masterchain block 2.4 s
run
19 Oct 2026 16:58 UTC · ✓ 20 of 20 reached in a masterchain block · 0.1 USDT each · rpc toncenter.com
docs
TON achieves transaction finality after a single masterchain block confirmation, typically within 1 second.the chain’s docs ↗ · read 18 Oct 2026
in a block — included in a block; HyperBFT commits in one step, so this is also final (done and final are the same level here)
slowest
in a block 2.8 s
run
19 Oct 2026 10:48 UTC · ✓ 20 of 20 reached in a block · 0.1 USDC each · rpc hyperevm-mainnet.infura.io
docs
The HyperEVM consists of EVM blocks built as part of Hyperliquid's execution, inheriting all security from HyperBFT…the chain’s docs ↗ · read 18 Oct 2026
finalized — finalized: two consecutive quorum certificates, the RPC's finalized tag
slowest
in a block 1.1 s→ finalized 3.0 s
run
19 Oct 2026 14:56 UTC · ✓ 20 of 20 reached finalized · 0.1 USDC each · rpc plasma-mainnet.core.chainstack.com
docs
Block finality is achieved in seconds with minimal communication overhead, and validator selection is driven by a…the chain’s docs ↗ · read 18 Oct 2026
confirmed — confirmed: a supermajority of stake voted on the slot
final
finalized — finalized: the slot is rooted and cannot be reverted
slowest
processed 1.2 s→ confirmed 1.2 s→ finalized 8.1 s
run
18 Oct 2026 21:18 UTC · ✓ 20 of 20 reached finalized · 1 USDC each · rpc solana-mainnet.infura.io
docs
A block the cluster recognizes as finalized with maximum lockout, meaning it has reached the strongest confirmation…the chain’s docs ↗ · read 18 Oct 2026
validated — in a validated ledger with tesSUCCESS: validators agreed on the ledger (done and final are the same level here)
slowest
validated 14 s
run
19 Oct 2026 17:01 UTC · ✓ 20 of 20 reached validated · 0.1 USDC each · rpc xrplcluster.com
docs
When the network agrees on the contents of a ledger version, that ledger version is validated , and its contents can…the chain’s docs ↗ · read 18 Oct 2026
in a block — included in a block by the sequencer — its word, not Ethereum's
final
L1 finalized — the batch holding the block is finalized on Ethereum
slowest
in a block 1.6 s→ posted to L1 73 s→ L1 finalized 17 min
run
19 Oct 2026 17:55 UTC · ✓ 20 of 20 reached L1 finalized · 0.1 USDC each · reads lb.drpc.org · sends rpc.xlayer.tech · the next sent once the previous was in a block
docs
Fast execution happens on L2 with 1-second block times.the chain’s docs ↗ · read 18 Oct 2026
in a block — included in a block by the sequencer — its word, not Ethereum's
final
L1 finalized — the batch holding the block is finalized on Ethereum
slowest
in a block 0.8 s→ posted to L1 6 min→ L1 finalized 19 min
run
19 Oct 2026 15:19 UTC · ✓ 20 of 20 reached L1 finalized · 0.1 USDC each · reads lb.drpc.org · sends arb1.arbitrum.io · the next sent once the previous was in a block
docs
Hard finality—the `safe` and `finalized` tags—is inherited from the parent chain and is what makes a block reorg-proof.the chain’s docs ↗ · read 18 Oct 2026
in a block — included in a block by the sequencer — its word, not Ethereum's
final
L1 finalized — the batch holding the block is finalized on Ethereum
slowest
in a block 0.9 s→ posted to L1 13 min→ L1 finalized 19 min
run
19 Oct 2026 15:38 UTC · ✓ 20 of 20 reached L1 finalized · 0.1 USDG each · reads lb.drpc.org · sends rpc.mainnet.chain.robinhood.com · the next sent once the previous was in a block
docs
Full finality — your transaction inherits Ethereum's security and is irreversible.the chain’s docs ↗ · read 18 Oct 2026
in a block — included in a block by the sequencer — its word, not Ethereum's
final
L1 finalized — the batch holding the block is finalized on Ethereum
slowest
in a block 1.3 s→ posted to L1 47 s→ L1 finalized 22 min
run
19 Oct 2026 15:59 UTC · ✓ 20 of 20 reached L1 finalized · 0.1 USDC each · reads base-mainnet.infura.io · sends mainnet.base.org · the next sent once the previous was in a block
docs
After roughly 2 minutes, a Base batch containing the transaction has been posted to Ethereum.the chain’s docs ↗ · read 18 Oct 2026
By design: a block every three seconds, but the docs call that pending; the only level Tron stands behind is "solidified", nineteen producers later, about a minute.
levels
in a block 3.0 s→ solidified 60 s
docs
Blocks become irreversible — solidified — once at least 19 distinct active SRs have each produced a block at that…the chain’s docs ↗ · read 18 Oct 2026
By design: a block about every ten minutes, and six of them is the custom, which the docs themselves call somewhat arbitrary.
levels
one confirmation 10 min→ six confirmations 60 min
docs
6 confirmations: The network has spent about an hour working to protect the transaction against double spends and…the chain’s docs ↗ · read 18 Oct 2026