Home/aztec/address/0xae27…671f
Address

0xae27…671f

ContractDemo Vaultcurated

0xae2774355390cef9b4e4a6e56c3e94d9fc98671f

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
Debug (divergent)0x0baa…4a96101:10x01c8…d9320xae27…671f0x1a2b3c4d42000 / 100000 manaSucceeded
Blocks 101 to 101 · segment 1 of 1

Code

Code hash
0xd85a99160aa0eb76d0792e7b1101dbb1bc9d1e48
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.