Address
0x18cd…06dc
Account0x18cd107332c12d2bdba8c8d3757822a91a8c06dc
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.
| Debug | Tx hash | Block | From | To / target | Method | Fee | Status |
|---|---|---|---|---|---|---|---|
| Generate trace | 0xfc0f…f376 | 100:3 | 0x18cd…06dc | 0x6f1b…c4a5 | 0x7f3e21c4 | 1874320 / 2000000 mana · 412800 / 500000 gas · 938114 / 1000000 gas · 6 / 8 slot · 24 / 64 count | Succeeded |
Blocks 100 to 100 · segment 1 of 1
Code
No code is bound to this address in the published tree, so it is an account rather than a contract. A code binding is published as a code edge on the transactions that ran it.
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.