Home/aztec/tx/0x050f…95af
Transaction

0x050f…95af

Succeeded

0x050f8e3acb1167de56ca757b9e64fb989788e82c55e2e21c8340e0deba3195af

click to select
Not 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 2 transaction(s) before it in block 31646, 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
6781504595951079720 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": 31646,
  "txIndexInBlock": 2,
  "revertCode": 0,
  "bodyRetainedAtCapture": false,
  "effectVisibleAtCapture": true
}