Real Aztec mainnet dataaztec-mainnet

Captured from aztec.drpc.org at 2026-08-31T07:39:12.420Z (node 5.2.0). The replay window was blocks 67120–67144 (25 blocks) at that moment. NO TRANSACTION INSIDE IT WAS REPLAYABLE, so this chain publishes real blocks and real transactions and no traces. That is what the capture found, not a failure to record. Across the 400 blocks enumerated here this chain settled 20 transaction(s), and they did not arrive evenly: the longest run with none was 309 blocks, and the most recent one settled in block 67113 — 7 block(s) below the window, so it had already been pruned when this capture ran. Catching one needs a follower that watches the tip continuously rather than a single scan. Transactions below block 67119 are still visible on the network but their bodies have been pruned, so they can no longer be replayed and carry no trace.

Home/aztec-mainnet/blocks/0x21eb…df8c
Block

Block 67111

Finalized
Height 67111 — the oldest block this generation indexes.
← PreviousNext →
Chain
aztec-mainnet
Hash
0x21ebf9dcfba9e6b0736c7a300b31f09b9497c8e73049429574eeb35ec90edf8c
Height
67111
Parent
0x145c08bd44418cc5442b86f30ea6a078d159e4b72542dfe40dccc4ac179b3308 — below this generation's floor, so there is no page for it here. The hash is the chain's; the page is this tree's, and this tree does not hold it.
Finality
Finalized
Transactions
1

Transactions in this block

DebugTx hashBlockFromTo / targetMethodFeeStatus
Not observable0x2b77…e17d67111:00x00000000000000000000000000000000000000000000000019ab3ba23c664052 manaSucceeded
Family extras have no field in the block object yet. §5.2's per-family zone — base fee and blob gas on an EVM chain, checkpoint and epoch on Move, slot and leader on Solana — comes from the adapter, and the published block object carries the chain, the hash, the height, the parent and the transaction list. A transaction already carries its chain-native payload verbatim; a block does not, and that is the field this zone reads when it lands.