Explorer Pages

Explorer Pages

A page-by-page reference for the explorer section of the node's embedded web UI. Each page fetches data from the node's HTTP API through the UI server's /api/* proxy.

Detail views are query parameters on the list pages rather than nested routes -- for example /accounts/?addr=<address> and /blocks/?hash=<hash>.

Overview (/)

The dashboard landing page.

Content:

  • Identity -- this node's account address and peer ID
  • Stats grid -- peers, accounts, blocks, pending, leases and providers, each with a delta and sparkline, linking to the matching page
  • Block rate chart -- last 5 minutes in 5-second buckets
  • Recent blocks -- time, type, account, asset, amount, balance and hash

Counters are rendered from a cached snapshot first so the page is populated before any network call resolves, then refreshed on a poll that pauses when the tab is hidden.

API: GET /node, GET /pending, GET /leases, GET /providers, GET /blocks/recent.

Accounts (/accounts)

All accounts on the network in a sortable table.

ColumnDescription
addressAccount address (truncated, with copy button)
xeCurrent XE balance
xusdCurrent XUSD balance
blocksNumber of blocks in the account chain
frontierHash of the latest block
last blockTimestamp of the most recent block

Clicking an address opens the account detail view.

API: GET /accounts (paginated).

Account detail (/accounts/?addr=<address>)

Full view of a single account:

  • Account -- full address, frontier, block count
  • Balances -- per-asset amounts
  • Multisig keyset -- shown when the account has one
  • Pending receives -- time, asset, amount, sender and send-block hash
  • Recent chain -- the tail of the account chain: time, type, asset, balance, hash

API: GET /accounts/{address}/balance, GET /accounts/{address}/keyset, GET /pending/{address}, GET /accounts/{address}/chain.

Blocks (/blocks)

Recent blocks across the whole network in a sortable table: time, type, account, asset, amount, balance and hash.

API: GET /blocks/recent.

Block detail (/blocks/?hash=<hash>)

Every field present on the block, rendered in a stable order and formatted by type:

  • Addresses (account, destination, provider, …) link to the account page
  • Hashes (previous, source) link to the block page
  • Amount fields (amount, balance, cost) are formatted from micro-units; cost is always XUSD
  • Emission-lock fields on lease_accept (locked_r, locked_payout_cap, locked_twap_milli) are formatted from their ×1000 fixed-point form
  • Timestamps show time-of-day plus a relative age

A raw section shows the block's JSON verbatim.

API: GET /blocks/{hash}.

Pending (/pending)

All pending (unreceived) sends across the network: time, amount, asset, from, to and send hash.

API: GET /pending (paginated).

Peers (/peers)

This node: address, peer ID, version, network ID, peer count.

Connected peers: peer ID, address, agent version, connection time.

API: GET /node.

Leases (/leases)

All compute leases in a sortable table.

ColumnDescription
hashLease block hash
consumerConsumer account address
providerProvider account address
costXUSD cost
stakeProvider stake
resourcesvCPUs, memory, disk
statusLease lifecycle state

API: GET /leases.

Lease detail (/leases/?hash=<hash>)

A single lease's full record, with consumer and provider linking through to their account pages.

API: GET /leases/{hash}.

Providers (/providers)

Provider nodes offering compute: account, capacity, used, active leases, total leases and last update.

API: GET /providers.

Frontiers (/frontiers)

Every account's frontier: account, frontier hash, block type, chain depth, last update and representative.

API: GET /frontiers (paginated).

Conflicts (/conflicts)

Open conflicts, grouped by the account and position involved, listing the competing block hashes and when the conflict was detected.

[!INFO] Info A conflict is recorded when two or more blocks on the same account share the same previous hash. See Conflict Detection for how they are resolved.

API: GET /conflicts (paginated).

State chain (/statechain)

The DAO state chain.

  • Tip -- latest index, hash and timestamp
  • Recent epochs -- tokenomics epoch records decoded from epoch.* KV operations
  • Recent state-chain blocks -- index, hash, operation count, signature count, timestamp
  • KV lookup -- fetch a single key
  • Browse KV -- the full key set, filterable by substring

API: GET /statechain/tip, GET /statechain/blocks, GET /statechain/kv, GET /statechain/kv/{key...}.

State chain block (/statechain/?index=<index>)

Detail for one state chain block: metadata, the operation list, the member signatures, and navigation to the neighbouring block.

API: GET /statechain/blocks/{index}.

See also