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.
0x24ae…6522
Succeeded0x24aef82c4e9eb1ac2c9c43b989d04e97f9cdd8a2b5c6d7174c22ae0f1f9a6522
No trace can be produced for this execution — a permanent answer rather than a failed fetch. The published reason states why.
The node still serves this transaction's effects but no longer serves its body: getTxByHash prunes at the finalized tip (block 67119 when this snapshot was taken) and getTxEffect does not. This transaction settled in block 66792, 327 block(s) below it. It can no longer be re-executed, so no trace was recorded for it.
Overview
- Block
- 66792:0
- Canonical
- Yes
- Finality
- Finalized
- Cost · transactionFee
- 0x0000000000000000000000000000000000000000000000007d07930f181f6e00 / mana (FeeJuice)
Decoded input
- Selector
- —
- Raw
- 0x
Events
Internal calls
State changes
Raw (chain-native)
{
"l2BlockNumber": 66792,
"txIndexInBlock": 0,
"revertCode": 0,
"bodyRetainedAtCapture": false,
"effectVisibleAtCapture": true
}