Networks and data sources
Switch networks in ATP Explorer and learn what chain data, sample data, unavailable and not deployed mean.
ATP Explorer reads one network at a time. This page explains how to switch networks, which states you can see, and what a snapshot is.
Implementation candidate
Switch network
Use the network control in the header. The whole Explorer follows it, and your choice is remembered. To link someone to a page on a specific network, add ?network=<id> to the address, for example /atoms?network=solana.
| Network | Status | What you see |
|---|---|---|
| BSC Testnet | Deployed | Ledger records read from the chain |
| Solana | Not deployed | Ledger pages say the network is not deployed yet. Configuration shows the recorded network facts |
No data from one network is ever shown under another. For the networks themselves, see Protocol networks.
Chain data and sample data
The Explorer has two ledger sources.
- Chain. The default. The Explorer reads the deployment over RPC and shows the result with an On-chain badge.
- Sample. An opt-in mode for running on example records without a network. A Sample data badge marks it. Only a self-hosted copy can run in this mode. See Self-host the Explorer.
If the RPC cannot be read, the ledger pages say so. Example records are never shown in place of real ones.
Ledger states
| You see | It means | What to do |
|---|---|---|
| On-chain badge | Records were read from the chain at the snapshot block shown in Status | Nothing |
| Ledger unavailable | The chain could not be read, or the deployment did not verify against its record. No records are shown, and nothing is substituted | Select Retry. Configuration and Verification keep working |
| Not deployed | The selected network has no recorded deployment | Switch to a deployed network |
| Sample data badge | This copy runs on example records | Treat every ledger figure as an example |
What a snapshot is
Each page shows the chain as it was at one finalized block. Before it shows any record, the Explorer checks that the contracts on chain are the ones in the deployment record. If they do not match, it withholds the ledger data. You can run the same comparison yourself on the verification page.
The Status control in the header lists the snapshot block, its time and the block range that was scanned.
Values that are not on chain
Some values are not stored on chain. The Status control lists them under "Snapshot notes".
- Deadlines are reconstructed from the Atom's verified history.
- Asset names and units are not on chain, so assets appear by id.
- Object labels of Atoms are not on chain.
The first page you open after a quiet period can take several seconds while the snapshot is read. Later pages are fast.