Home/aztec-testnet/tx/0x176c…e5df
Transaction

0x176c…e5df

Succeeded

0x176c48c455fa3d8117869fa0298bf9acf4d788af79c86053839502ee7a29e5df

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.

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 23611 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
1008348139836009000 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": 23611,
  "txIndexInBlock": 0,
  "revertCode": 0,
  "bodyRetainedAtCapture": true,
  "effectVisibleAtCapture": true
}