Address
0x01c8…d932
Account0x01c8f081e2abedf0184953e2a272b5e430d5d932
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 |
|---|---|---|---|---|---|---|---|
| Debug | 0x5c67…f8df | 102:1 | 0x01c8…d932 | 0xc699…f6cb | 0x1a2b3c4d | 42000 / 100000 mana | Succeeded |
Blocks 102 to 102 · segment 1 of 3
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.