dashboard
Private read models of an account (usage, latency, notices, served-by relayers, outages).
The accounts the token's address can open in the dashboard.
Lists the accounts the token's address owns or is an authorised sender of. Each account's `role` picks
Money timeline of the account - deposits, plan purchases, renewals, skipped renewals, escrow moves, PAYG settlements, sender fees, grants.
Built only from finalised contract events, so it is public. Newest first.
Pollable notices - account notices plus global ones (tariff, RU schedule, incidents).
Pollable notices - account notices plus global ones (tariff, RU schedule, incidents).
Acknowledge notices up to a sequence number (idempotent).
Acknowledge notices up to a sequence number (idempotent).
'Their relayers' under just-in-time assignment = the relayers that served this account, with counts and on-chain state.
'Their relayers' under just-in-time assignment = the relayers that served this account, with counts and on-chain state.
Public incidents that overlapped the account's traffic, with the account's own impact numbers.
Public incidents that overlapped the account's traffic, with the account's own impact numbers.
Full transaction history of an account - every terminal intent incl. `DEAD` - with per-transaction latency breakdown in ms.
The account's transaction history, one row per transaction hash. It holds **every terminal intent,
Usage versus cap - period totals plus a bucketed time series (RU, tx count, fail count, latency percentiles), top senders and receivers.
RU and money totals count **billed rows only** (`billed = true`). `DEAD` and `REJECTED` rows appear
Latency analytics of an account - percentiles, server-side histogram bins and sampled points per group (shard, relayer, sender or gateway).
Served from pre-aggregated per-minute and per-hour latency histograms, grouped by `relayer`, `sender`
One row of the transaction history: the billing details when it was billed, the latency breakdown, the settlement batch and the gateway acknowledgements.
One row of the transaction history: the billing details when it was billed, the latency breakdown, the settlement batch and the gateway acknowledgements.
Merkle inclusion proof of a ledger row against the on-chain `usage_root` of its settlement batch.
Merkle inclusion proof of a ledger row against the on-chain `usage_root` of its settlement batch.
Server-sent events for one account (intents, quota, account mirror, notices, incidents, pricing).
Auth: send the `Authorization` header from a streaming HTTP client. From a browser `EventSource`,