0x27e2…5d13
Succeeded0x27e2ff4e69d175db7c8af65040d0af5d6408c0644a5017a3346334a9835c5d13
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 and getTxEffect does not. It was already below the replayable window when this follower first saw it, so it can no longer be re-executed and 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
- 1768894284667172100 mana (FeeJuice)
Decoded input
- Selector
- —
- Raw
- 0x
Events
Internal calls
State changes
Raw (chain-native)
{
"l2BlockNumber": 67242,
"txIndexInBlock": 0,
"revertCode": 0,
"bodyRetainedAtCapture": false,
"effectVisibleAtCapture": true
}