Cluster overview
Convergence over time
X-axis = block height (the cluster tip), last ~100 blocks. Height lag = max−min height across reachable nodes; tip divergence = distinct tips − 1 (0 = fully converged, 1 = a 2-way fork, etc.). Sampled every few seconds and kept per block height (worst case at each height), so transient forks show as spikes that should fall back to 0 on both charts. History persists in this browser across reloads. [clear history]
Per-node status
Polled every 10s. Backend list source: …
(discovery = live from the discovery service, saved to browser cache;
cached = localStorage peer cache from a prior discovery response — discovery currently unreachable;
static = hardcoded config.js list — last resort when both discovery and cache are empty;
override = ?node=… URL param).
What appears here: nodes registered with the discovery service (or the static fallback list). In a fully-configured cluster every node registers on startup, so discovery and gossip converge to the same set. The section below surfaces any extras found only via peer gossip.
| Status | Name | URL | Height | Tip | Role | Peers | Mempool | Mining | Consensus | Stake | Last heartbeat | Version |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Loading… | ||||||||||||
Gossip-only peers
Nodes whose wallet address appears in the /peers list of registered nodes
but who have not registered with the discovery service.
They reached the network through peer-to-peer gossip rather than registration.
Nodes with no browser-reachable public URL cannot be polled here —
their address is shown so an operator knows they exist.
Scanning…
| Wallet address | Internal URL | Type | Seen by |
|---|