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/0x144e…e2a0
Block

Block 63651

Unfinalized
Height 63651 — the oldest block this generation indexes.
← PreviousNext →
Chain
aztec-testnet
Hash
0x144e896df63357516e32c73e359ea62255273d157aa6cbc3ffea58152e8ae2a0
Height
63651
Parent
0x0058ded35c02771cb4af8b03828a40c30f9e59a4a22edace390f2056f1071609 — 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
Unfinalized
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.