Status
What each moving part last did, and when. There is no overall green tick here: a dashboard that is green because it is broken is worse than no dashboard.
MEASUREDRead live from the database and the chain on every request. Nothing on this page is cached, and no uptime percentage is shown, because we do not run an external prober against ourselves and would have to invent one.
Real-world usage
MEASURED18 anonymous product events, since 2026-09-08. No PII: an event name and, at most, a category or a count. Counted, never extrapolated.
| What | Count |
|---|---|
| independent agent tests | 1 |
| agents added to a comparison | 16 |
| preflights run | 1 |
Chain and index
| What | Value | Last moved | |
|---|---|---|---|
| BSC head | 120684205 | read just now | live |
| scan:list:56 | 310100 | 60 min ago | fresh |
| Pool tick watcher | 12104 observations across 7 pools | 1 min ago | fresh |
The registry index is an offset into 8004scan’s listing, not a block height, so “blocks behind” does not describe it. What matters is when it last advanced, which is what is shown. The pool watcher IS block-shaped and is the one that must not go quiet — the hours-out-of-range figure on the PancakeSwap Desk is only as dense as this series.
Probe coverage
| Latest verdict | Agents | Share |
|---|---|---|
| unbound | 23,903 | 78.7% |
| live | 6,114 | 20.1% |
| dead | 329 | 1.1% |
| bad_schema | 11 | 0.0% |
One row per agent, its most recent verdict only. unbound is a first-class outcome, not an error: the endpoint answers with a valid card that declares no endpoint and no skills, so there is nothing to call. A probe that only checked for HTTP 200 would count every one of those as healthy.
Reference agents
| Agent | Health | Round trip | Detail |
|---|---|---|---|
| bound | answers | 101 ms | answers |
| lattice | answers | 73 ms | answers |
| sluicegate | answers | 79 ms | answers |
| keel | answers | 69 ms | answers |
| redcell | answers | 66 ms | answers |
Checked on this request, through the public HTTPS path a buyer would use — including TLS and the reverse proxy, because a buyer waits for those too.
Conformance
| Test | Runs | Passes | Last run |
|---|---|---|---|
| MCS-GRID-1 | 177 | 6 | 2026-09-08 09:53 |
| MCS-HF-1 | 177 | 6 | 2026-09-08 09:53 |
| MCS-REB-1 | 177 | 4 | 2026-09-08 09:53 |
| MCS-YIELD-1 | 177 | 5 | 2026-09-08 09:53 |
Test stubs are excluded. Every pass recorded so far belongs to a first-party reference agent — no third-party agent on BNB Chain has passed an MCS test yet, and that is the measured state of the supply rather than a filter. The Standard lists the failures with their reasons. Last run 4.3 h ago.