24h sample: 565–615 TH/s; mean 594.1 TH/s. Fixed fictional readings.
| WORKER | STATE | HASHRATE | TEMP. |
|---|---|---|---|
| sm-01 | Online | 200 TH/s | 62°C |
| sm-02 | Online | 200 TH/s | 64°C |
| sm-03 | Warning | 200 TH/s | 78°C |
| sm-04 | Offline | 0 TH/s | — |
4 of 4 sample workers shown.
What this dashboard shows
This is a fixed, fictional sample captured at the displayed timestamp. There are four workers: two online, one in a warning scenario, and one offline. The three reporting workers each contribute 200 TH/s and 4,000 W in the sample.
Use the chart buttons to inspect three authored history windows. On this page, the worker filters show all workers, online workers, or workers needing attention. Those controls change the view locally; they never contact hardware.
Keep measurements and interpretation separate
Hashrate and power are sample measurements. Status is an authored interpretation. The warning temperature is illustrative, not a universal limit for mining equipment. A missing temperature is displayed as a dash and stored as null, not turned into zero.
The displayed 20 J/TH ratio is 12,000 W divided by 600 TH/s. Read the efficiency guide before adapting that calculation to a different measurement boundary.
Freshness is part of the evidence
The timestamp remains fixed because the underlying data is fixed. This is not a service-status page or a real-time feed. A production monitor should separately represent source time, collection time, collector availability, and worker state.
The monitoring design guide explains how those distinctions prevent a stopped collector from leaving a deceptively healthy dashboard.
Take the sample into your own prototype
Download the worker records, fleet summary, or history samples. The API reference documents each field.
When moving beyond synthetic data, keep device credentials out of browser code and restrict control operations to a separate authorized system. A useful observation interface does not need permission to modify equipment.