0x2044…6314
Succeeded0x2044a7c06467421fcd3bf901a46744115e9e95d0a7597f48a4a3a66f47886314
click to selectNo 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 66752, 367 block(s) below it. It can no longer be re-executed, so no trace was recorded for it.
Overview
- Data
- Real Aztec mainnet data
Captured from aztec.drpc.org over a watch that began 2026-08-31T07:39:12.420Z and was last extended 2026-08-31T17:13:36.084Z (node 5.2.0). The replay window was blocks 67587–67611 (25 blocks) when it was last looked at. 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 867 blocks enumerated here this chain settled 25 transaction(s), and they did not arrive evenly: the longest run with none was 309 blocks, and the most recent one settled in block 67511 — 76 block(s) below that 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 67586 are still visible on the network but their bodies have been pruned, so they can no longer be replayed and carry no trace.
- Block
- Type
- public
- Age
- No timestamp published
- Canonical
- Yes
- Finality
- Finalized
- Cost · transactionFee
- 8991448229252641098 mana (FeeJuice)
Decoded input
- Selector
- —
- Raw
- 0x
Events
Internal calls
State changes
Raw (chain-native)
{
"l2BlockNumber": 66752,
"txIndexInBlock": 0,
"revertCode": 0,
"bodyRetainedAtCapture": false,
"effectVisibleAtCapture": true
}