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/0x1214…bb52

Block

Block 66950

Finalized

Chain: aztec-mainnet
Hash: 0x1214504f781eda0c6db66ba2697e3c57fb714b388c2276dc5511e3a88ebdbb52
Height: 66950
Parent: 0x2184d7e21b8521d99c4f875336495e02779460f73e76f1700396c11b40eb7a47 — 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: 0

Transactions in this block

Debug	Tx hash	Block	From	To / target	Method	Fee	Status
This block carried no transactions. That is a fact about the block, not a gap in the index — the block object lists its transactions and this one lists none.

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.