Data Freshness

The indexer follows the chain head with a two-block lag. Freshness on the Status page is that lag, not a marketing SLA.

Live tables typically trail the head by two blocks. Token transfers may trail by one additional block while the decoder commits.

The Status page exposes latest block, indexed block, lag and missing blocks. Missing blocks is 0 in the steady state; a non-zero value is an incident.

API responses that include a block_number can be compared to /v1/arc/blocks/latest to measure lag from the client side.