XEN Dashboard data methodology
Browser RPC, published snapshots, update cadence, launch coverage, missing values and limits of XEN Dashboard's data.
Documentation reviewed
This is a documentation review date, not the timestamp of live data.
Two complementary read paths
The browser reads current Ethereum state and recent logs from the configured public RPCs. Summary and historical charts also use the existing static JSON publication. Market quotes come from the configured Ethereum XEN pair on DexScreener.
A Manifest names immutable snapshot files with byte counts and SHA-256 hashes. The page verifies the referenced data rather than joining arbitrary files from different publications. RPC and published data can refer to different blocks or times; they are not one atomic live snapshot.
Cadence and confirmation delay
The server schedules Summary every ten minutes, with up to 30 seconds of randomized delay, and History hourly, with up to three minutes of randomized delay. RPC work can add delay. Read generatedAt, source block and freshness rather than treating the schedule as a delivery guarantee.
History advances through the Collector's confirmed head, which trails the tip. The newest indexed hour can still be incomplete. A currently unfinished hour is not automatically a collection gap. This documentation does not change collection or start a manual read.
Launch coverage and range buckets
From launch means this dashboard's collection window, beginning at Ethereum block 25,501,848; it does not mean the whole life of XEN. Current Supply is a contract-state reading, not a sum of only those launch-window events.
D7 uses hourly points, D30 and D90 daily buckets, and ALL weekly buckets. Wider buckets use the latest measured point in the bucket, not an automatic sum of hourly flow fields. For interval flows use the appropriate hourly values or differences between cumulative counters. Unfinished day/week buckets can change as new hours arrive.
Missingness and recent claims
A null or unavailable value is not zero. missingRanges describes uncovered history; a measured zero event count can be a valid observation. Unknown future hours and rolling points leaving a window are not missing historical collection.
The Collector retains up to 3,000 recent rank claims in complete blocks; an initial read-back is bounded to 7,200 blocks. It is a recent record, not a full event archive. The galaxy and Miners can extend a quiet two-hour window to 3, 6, 12 or 24 hours only when complete coverage joins the browser's own block range.
Health and optional estimates
Health's 26/26 critical-field coverage checks the required current fields and publication integrity. It does not certify every upstream value or establish full protocol-lifetime history.
Claim-cost measurement is optional and expires after three hours. A missing cost estimate is not zero cost. Failed or unavailable upstream reads can leave the last valid data or an unavailable section; documentation does not override those states.