Node status

A Rustock instance following RSK mainnet. Read-only JSON-RPC, polled once a minute.

Rustock · RSK Mainnet refreshed every 60s
Best block
—
Peers
—
Chain state
—
Distance to tip
—
Client
—
Network
—
JSON-RPC · read-onlyconnecting…

What you are looking at

A single Rustock node, synced from genesis, executing every block and comparing every state root against the header it came in. It is not a network-wide explorer and it does not speak for Rootstock — it is one node's view, published because a node implementation should be able to show you that it works.

Where the numbers come from

A small proxy calls four read-only methods and caches the answer for a minute. Nothing else is exposed, and no method that changes state is reachable through it.

eth_blockNumber      // best block
eth_syncing          // current vs highest
net_peerCount        // connected peers
web3_clientVersion   // build identity

If the panel says unreachable, the node is restarting or resyncing. That is left visible on purpose rather than hidden behind a cached last-known-good value.