Real Aztec testnet dataaztec-testnet

Captured from aztec-testnet.drpc.org at 2026-08-31T07:40:55.566Z (node 5.2.0). The replay window was blocks 63629–63678 (50 blocks) at that moment. 6 transaction(s) inside it were re-executed and their traces are published here. Transactions below block 63628 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-testnet/blocks/0x1b10…288a
Block

Block 63561

Finalized
Height 63561 — the oldest block this generation indexes.
← PreviousNext →
Chain
aztec-testnet
Hash
0x1b1087eb79f049a9c6db71810794ea9a393a29dff9de8cdd9bf5d8016f52288a
Height
63561
Parent
0x0ee5e1a264875e2df8371b0e09e8396f282c6653a2f1dcd5a55712eaddea5956 — 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

DebugTx hashBlockFromTo / targetMethodFeeStatus
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.