Explorer pages
What each ATP Explorer page shows, from Overview and Atoms to disputes, settlement, assets, search, transactions and addresses.
This page describes each page of ATP Explorer and how to read it. Every ledger page follows the network you selected in the header. See Networks and data sources.
Page map
| Route | Page |
|---|---|
/ | Overview |
/atoms, /atoms/[id] | Atoms and Atom detail |
/disputes | Disputes |
/delegations | Delegations |
/settlement | Settlement |
/assets | Assets |
/configuration | Configuration |
/lookup?q= | Search |
/tx/[hash] | A transaction |
/address/[address] | An address |
/sessions/[id] | A delegation session |
/verify | Deployment verification |
Overview
Overview shows what is happening now.
- Four figures: Atoms in flight, open disputes, Atoms finalized in the selected range, and timeouts that anyone can execute now.
- Finalized by outcome: Atoms finalized per UTC day, by terminal outcome. The chart opens on the shortest range that contains data.
- Finalization routes: how finalized Atoms reached their terminal state. Dispute routes are always listed, even at zero.
- Escrow locked per token: one row per token. Amounts of different tokens are never added together.
- Needs attention: executable timeouts and case deadlines that have passed or fall within three days.
- Recent activity: the newest protocol events.
Atoms
The Atoms page has one row per Atom: id and creation date, state, outcome and route once finalized, buyer and seller, value, fee class, and the next deadline. "Executable now" on a deadline means the deadline has passed and anyone may call the timeout.
Use the filter bar to narrow by state, outcome, route, token, fee class, completion mode or executable timeout. Use the search field for an Atom id or a root address. You can sort by value, creation date and next deadline.
Select an Atom to open its detail page:
| Tab | Shows |
|---|---|
| Overview | An alert when a timeout is executable or a dispute is open, every deadline and whether it has passed, the settlement terms, and (once finalized) the split with a conservation check |
| Lifecycle | Every contract event for the Atom, one step per transaction |
| Dispute | The case, if the Atom has one, with a link to it in Disputes |
| Raw record | The record as JSON |
The side column holds the parties and terms, which never change after creation. Add ?tab=lifecycle to a link to open a tab directly. For the lifecycle itself, see Atoms and lifecycle.
Disputes, delegations, settlement and assets
Disputes lists cases by phase: negotiation, arbitration and consumed. Each row shows the negotiation deadline (Tn), the time when an independent award becomes possible (Tn + 14 days), which filings are recorded, and how a consumed case was decided. Select a case to open its sheet with the facts, the routes available right now and why, the ordered case trace, the signatures and the raw record. A case whose Tn has passed but which has not been advanced is flagged "Tn passed". The stored phase is shown as it is on chain. Link to a case with /disputes?case=<label>.
Delegations lists sessions a root has granted to a delegate: side, lifetime and expiry, status, permitted actions, and spending against the lifetime cap. Select a session for its full terms and consumption history. A delegate can never open a dispute, file in a case or sign consensus. See Delegation.
Settlement is scoped to one token at a time. Choose the token at the top right.
- Totals: escrow the vault accounts for, paid to sellers, refunded to buyers, protocol fees, and dispute fees held.
- Conservation: buyer out + seller out + company fee + ecosystem fee + held dispute fee must equal the escrow settled. The alert turns red if it does not.
- Vault: what the vault holds against what it accounts for.
- Tables and charts: escrow flows, fees by class, fee claims and receipts. Receipts are a projection made after finality and are never part of settlement.
See Fees and settlement for the rules behind these numbers.
Assets is an inventory with total, available and reserved units and terminal dispositions. Select an asset for its reservations and a conservation line. Asset names and units are not stored on chain, so on-chain assets appear by id.
Configuration
Choose the recorded deployment at the top right. Configuration has five tabs.
| Tab | Shows |
|---|---|
| Overview | Deployment facts and a live check of the deployment against the chain |
| Modules | Each contract's address and, for the bound deployment, whether code is present and its runtime hash matches the record |
| Configs | The admission config, fee rates, drain counters and admitted tokens |
| Authority | Roles and treasuries, the authority profile and the award committee |
| Networks | Network facts and notes |
A red marker on a tab means the live check found a mismatch there. See also Verify a deployment.
Search, transactions, addresses and sessions
Search is the header field, or Ctrl K. It accepts an Atom id, a delegation session id, a transaction hash, an address, or an Atom locator in the form evm:<chain id>:<AtomCore address>:<Atom id>. It opens the page for the value, or tells you what it did not find and why. A locator for another chain or another AtomCore says which part differs. The same search runs at /lookup?q=.
Transaction (/tx/<hash>) shows:
- status, block and finality;
- what the transaction did, in one sentence;
- the protocol events in the order they were emitted, with the module that emitted each;
- the revert reason, if it reverted.
A transaction that did not call the deployment and emitted none of its events is labeled "not an ATP transaction".
Address (/address/<address>) tells you whether the address is a protocol module, a settlement token or an ordinary address. It lists the Atoms (as root buyer, root seller or payer) and delegation sessions (as root or delegate) the address takes part in.
Delegation session (/sessions/<id>) gives a stable link to a session's terms and consumption history. An Atom's detail page shows its locator with a copy button.
Rate limits
When a client asks the Explorer for chain data too often, it answers "Too many requests" and tells you how many seconds to wait.