Account blocks per momentum no linkcarries a link, relayed
Seconds between momentums a slot is 10 s; a longer gap is a slot nobody filled
Nodes the line beside a value is its history over the range; hover it for a reading
Where each number comes from
CPU, memory, network, block writes: docker stats, one call for every running container each round. CPU is percent of one core, so a node hashing a hop on one thread reads near 100. Network is the average rate over the range, from docker's running totals.
Disk: du of the node's data directory, every 30 s. Frontier: ledger.getFrontierMomentum where the node publishes a port, else the last momentum its log says it inserted. RPC: how long that call took from this host.
Arrival: the node's log time for the newest momentum it inserted, minus that momentum's own timestamp. The log's clock ticks in seconds, so a reading is true to a second. Peers told: how many peers the node last announced a momentum to, from the same log. A Sentinel's stats.* methods are off its public allowlist, so its peer count is not asked for.
Hops, hop work, pending: sentinel.stats, counted since the node started. Hop work is the mean time one hop's proof of work took.
Momentums, throughput, relayed share: ledger.getDetailedMomentumsByHeight on rpc. Throughput counts account blocks of every kind, the contracts' own included, over the range. History lives in the console server's memory for an hour and starts when this page is first opened.