Skip to content
IceRootDocs

Use the explorer

Find a record, then follow its links: transaction to block, wallet to history, or validator to activity.

The read-only explorer at scan.iceroot.com reads the public lab devnet through a relay API, the reference API node. It shows live blocks, transactions, wallets, delegates, rounds, search and network status. This network has no value and may be reset at any time. See Network status.

The explorer reflects one relay’s view. It is not a source of truth for exchanges or custody. It reports the pinned network hash (nethash) and refuses a different chain.

The backend refreshes about every 30 seconds by default. Browser polling follows the configured block time. A chain tip older than 60 seconds is labelled stale. Confirmation labels follow the current chain rules: the lab chain has no deterministic finality. The default confirmation threshold is six blocks; even a confirmed block is labelled not final.

PageUse it for
OverviewA quick glance at network activity
BlocksA block’s transactions and its place in history
TransactionsIndividual actions and their details
ValidatorsValidator activity and recorded rounds
AssetsMulti-asset records are unavailable on this network
WalletsLook up an address for balances, transactions, and votes
MigrationsNo migration records or routes are available on this network
  1. Paste a transaction ID, wallet address, block height, or validator identifier into search.
  2. Choose the matching result type.
  3. Open the record to see its details and related activity.

Multi-asset records are not available on the lab devnet.

The draft protocol proposes an asset page with a descriptive lifecycle label, such as Active or Rooting. Labels are derived from the asset’s counters and records and never freeze transfers; see Lifecycle labels.

The draft protocol proposes migration views with the class of each source network and destination, classical or post-quantum, and a classical one’s cut-off. See Migrations and continuity.

  • Blocks: select a block to inspect it, or use playback to move through recorded history.
  • Validators: follow a recorded round, including empty missed slots.

Motion pauses when the view is hidden and respects reduced-motion preferences.

These proposed views are unavailable on the live lab explorer.

The draft protocol proposes explorer views for seats and vote weight per declared operator and per hosting provider, and how much of each validator’s vote weight comes from addresses its validator account funded directly. Relationships are described with these terms:

  • Declared same operator: validators whose declarations name the same operator.
  • Observed funding relationship: one account funded another on chain.
  • Shared infrastructure: validators that use the same hosting provider, according to their declarations or other observable evidence.

These views help you weigh concentration before voting. They report what is declared or observable, not proof of independence or of common ownership, and ownership that nobody discloses can stay hidden.

This proposed page is unavailable on the live lab explorer.

The draft protocol proposes a Genesis distribution page that reads the labeled genesis pool accounts live. For each pool it shows the allocation and the ROOT that is locked, unlocked, and distributed. Payouts from the five program pool accounts link to the program list using the entry id and 64-character fingerprint in their memo. The explorer reads the same files as the public list in iceroot-network/programs. Payouts to parties related to the IceRoot team are marked as related-party, with the relationship stated. The team’s on-chain lock appears there as time-locked entries with their unlock times.

Only the Security and bug bounty, Developer ecosystem, Ecosystem campaigns, Long-term reserve, and Community and ambassadors pool accounts follow the list. The Team account and the Development and Ecosystem funds show balances and transfers without program entries. Participation shares and earned pre-mainnet bounties appear as direct genesis credits.

The page states that IceRoot has sold no ROOT. That is a commitment, not a proof: a private sale would look like an ordinary transfer. ROOT supply and distribution describes the pools and their programs.

Use Retry when the explorer reports that its API is unavailable. If the connection fails after records have loaded, the page reports the disconnection and keeps the last received records on screen while it reconnects. These are retained records, not current network state. An empty or failed response should not be interpreted as a zero balance or an idle network.

Developers can use the explorer API reference to work with the same records.