stats

Latency budgets and data-freshness anchors of the service, for one chain (Base by default)

The answer is about one chain: chain_id names it, and chain_source is explicit when you passed chain or default when you did not and got Base. graph_batch and signal_firing are per chain (scope: chain), ofac_sanctions is global, latency rows are per API process. The graph batch runs weekly: an anchor within budget_seconds is under budget, and a last_refresh older than the latest weekly run means that chain's run did not land. Indexing freshness per chain is /v1/sync/status, not this.

get/v1/stats/slo

Request

  • Base URL: https://stablescan.achivx.com
  • URL: https://stablescan.achivx.com/v1/stats/slo
  • Auth: none required

Query parameters

1 | 10 | 56 | 8453 | 42161 | 728126428 | -1
OR
'1' | '10' | '56' | '8453' | '42161' | '728126428' | '-1' | 'ethereum' | 'optimism' | 'bnb-chain' | 'base' | 'arbitrum' | 'tron' | 'solana' | 'eip155:1' | 'eip155:10' | 'eip155:56' | 'eip155:8453' | 'eip155:42161' | 'eip155:728126428' | 'solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp'

Pass it explicitly — silent default is Base (8453); an answer about the wrong network looks exactly like an answer. Accepted as the number, the number in a string, the network slug (ethereum, bnb-chain, … from /v1/networks) or the CAIP-2 id. Surrounding whitespace, a leading + and leading zeros are ignored, slugs and CAIP-2 ids match in any letter case, and an empty or blank value is the parameter left off (/v1/freezes/acts alone refuses it).

Response

Latency budgets and freshness anchors of one chain — chain_id names it; without chain it is Base.

as_ofstring required
chain_idinteger required

The chain the per-chain rows (scope chain: graph_batch, signal_firing) are about. Without chain it is Base (8453).

chain_sourcestring required

explicit (you passed chain) or default (no chain was passed, so the answer is about Base).

notestring required

Changes

No recorded changes to this operation across all 1 revision of this API.