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/0x071b…e7cd
Block

Block 66749

Finalized
Height 66749 — the oldest block this generation indexes.
← PreviousNext →
Chain
aztec-mainnet
Hash
0x071b13d220e6e2678d4e34620adfa7867f2e6ae2896defc879d94c615f28e7cd
Height
66749
Parent
0x10fea6557be157e609e84dad9731035f9a7cb1395dbe5e6373bd437e2cbdebda — 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 observable0x20d2…f40966749:00x0000000000000000000000000000000000000000000000007c68eb7d66d22ad9 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.