Home/aztec/address/0x6f1b…c4a5
Address

0x6f1b…c4a5

ContractDemo Tokencurated

0x6f1bca903ca8990970644094358a27014ee6c4a5

Transactions

Complete history, one block-range segment at a time. There is no record cap and no capability to negotiate: the pipeline builds this index, so every listed chain has all of it.

DebugTx hashBlockFromTo / targetMethodFeeStatus
Debug0xa459…9296100:00x37c4…79a20x6f1b…c4a50x1a2b3c4d42000 / 100000 manaSucceeded
Generate trace0xfc0f…f376100:30x18cd…06dc0x6f1b…c4a50x7f3e21c41874320 / 2000000 mana · 412800 / 500000 gas · 938114 / 1000000 gas · 6 / 8 slot · 24 / 64 countSucceeded
Blocks 100 to 100 · segment 1 of 1

Code

Code hash
0x7f49e2edfb2c3ec8e852a8f8441c9ca2ea0b7f80
Verification
full match via demo-vendored
Compiler
nargo 1.0.0-beta.26
Language
noir

Browse the verified source →

Events

Logs emitted by this address come from a log index the published tree does not carry yet. The transactions above carry their own raw logs, and this section fills in when the pipeline publishes the per-address index — it is not a statement that this address emitted none.
Balances and token holdings are out of scope in V1, not missing. They are the account-explorer data model, with their own aggregates, their own reorg-recomputation surface and their own correctness problem. This page earns its place by listing executions.