0x7975…1064

Succeeded

0x7975216719d3f981e5ab9f63f0c9192f98981064

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.

executed entirely client-side in the private kernel; only proofs, nullifiers and commitments are published, so there is no call structure to trace

Overview

Data: Synthetic demo data; Every block, transaction, address and hash on this chain is generated from a fixed seed. None of them exists on any network, and none of these values can be looked up anywhere else. The execution trace is real — it is a recorded Noir program — but it is not the execution of the transaction it is published under.
Block: 100:4
Type: private
Age: No timestamp published
Canonical: Yes
Finality: Finalized
Fee payer: 0x37c434bdcb21f8ae8d0068e440bbd34b1b8b79a2
Target: 0x6f1bca903ca8990970644094358a27014ee6c4a5
Cost · Mana: 42000 / 100000 mana (FeeJuice)

Decoded input

Selector: 0x1a2b3c4d
Raw: —

This selector is not in any ABI BlockTracer holds, and no call data accompanies it here, so there are no parameters to decode. An ABI would not help, and BlockTracer cannot yet be given one in any case.

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)

{
  "aztec": {
    "kind": "private",
    "privateFunctions": [
      "transfer"
    ]
  }
}