Network
The coordination layer is event-sourced: every state transition emits a signed protocol event. This is the Devnet cluster, contacted live when the page loads.
Nodes
Contacting the nodes this build knows about…
Everything under Claims comes from the node's own registration, signed by its own key: it is what the operator configured, and nothing here verifies any of it — including the name it calls itself and the region it declares, which nobody measures. Observed, latency and status come from a live request to each node when this page loads — that is the part that was checked, and latency is measured from your browser, so it answers "is this node fast for me" better than any declared region could. Peer counts and versions are per node rather than per row and are under Your access node below, because they are one node's view of the network rather than the network's.
Your access node
Everything below is your access node's own answer about itself — its peer table, and the snapshots it knows about. Another node will give different figures for all of it, honestly: a peer list is one node's discovery cache, and latency and exchange counts are its own experience of each peer rather than anybody's verdict.
Peers
Asking the node…
Snapshots
A snapshot is how a new node joins without replaying all of history. It matters in both directions: an operator bringing a node up downloads one, and anybody choosing an access node can read from the age of the newest one roughly how long that node has been paying attention.
Asking the node…
A snapshot carries a 32-byte state root, and this page deliberately does not show it. Rendering a digest here would read as verification, and nothing a browser does verifies anything about it: the signature and registration checks a node performs establish that the bytes are what the announcer said, not that the announcer told the truth — which is why a node's first snapshot has to come from a pinned anchor rather than from whoever answered. The producer is shown instead, because that is the part you can look up in the service registry.
Looking for the signed event feed? The explorer subscribes to it from your access node. Services that nodes consume — oracles, notification gateways, risk intelligence, snapshots — are in the service registry, not here: they are not endpoints an interface connects to.