Transaction
0x210f…67dc
Succeeded0x210f25afc734e3ebe98f10f4e0482f8744d735f7b4e1e3ec0dea26dfc08867dc
click to selectNot observable
No trace can be produced for this execution — a permanent answer rather than a failed fetch. The published reason states why.
Refused — Replaying this transaction needs the state left by the 3 transaction(s) before it in block 9238, and the node does not serve intra-block intermediate state — it exists only inside the sequencer that built the block. Only the first transaction in a block can be re-executed from published data, so no trace was recorded for this one.
Overview
- Data
- Real Aztec mainnet data
Blocks and transactions taken from the live network. This is a preliminary export covering 14 July to 28 September 2026.
- Block
- Type
- public
- Age
- No timestamp published
- Canonical
- Yes
- Finality
- Finalized
- Cost · Transaction fee
- 1231975126592877618 mana (FeeJuice)
Decoded input
- Selector
- —
- Raw
- —
BlockTracer holds no call data for this transaction, so there is nothing here for an ABI to decode. Whether none was published or the body was pruned before it was captured is not something this section can tell; where that is known, it is stated above.
Events
Events come from the transaction receipt, not from a trace. They appear here once this chain's receipts are published.
Internal calls
Internal calls come from the execution trace. No trace was recorded for this execution and none can be now, so this section is empty permanently, not yet.
State changes
State changes come from the execution trace. No trace was recorded for this execution and none can be now, so this section is empty permanently, not yet.
Raw (chain-native)
{
"l2BlockNumber": 9238,
"txIndexInBlock": 3,
"revertCode": 0,
"bodyRetainedAtCapture": false,
"effectVisibleAtCapture": true
}