Transaction
0x106d…bf64
Succeeded0x106df482ec31a1994e2c0bee47f4137364c360871e929484f843a27fc1e1bf64
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.
This transaction has no public execution to trace. Its private half ran in a wallet and was proved there; what the chain published for it in block 54951 is the effects of that proof and nothing else, so there is no public bytecode, no enqueued call and no execution to re-run. Nothing declined this transaction — the execution was never public.
Overview
- Data
- Real Aztec testnet data
Blocks and transactions taken from the live network. This is a preliminary export covering 13 July to 28 September 2026.
- Block
- Type
- public
- Age
- No timestamp published
- Canonical
- Yes
- Finality
- Finalized
- Cost · Transaction fee
- 1011664148222598000 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": 54951,
"txIndexInBlock": 0,
"revertCode": 0,
"bodyRetainedAtCapture": true,
"effectVisibleAtCapture": true
}