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/0x0639…1eb8
Block

Block 66785

Finalized
Height 66785 — the oldest block this generation indexes.
← PreviousNext →
Chain
aztec-mainnet
Hash
0x0639c7d00cbe3fd30c13648819c56fb2918f30cd7b8417271574107374421eb8
Height
66785
Parent
0x1932ace8f1f158a2d3da5e76cff1c0d7ccc376f58f4c5e58e3d995b2ef04ad8e — 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 observable0x2375…685966785:00x0000000000000000000000000000000000000000000000001e347ce63aa683d6 manaReverted
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.