Status
Indexer and services
Live health of everything DEVOXPAD reads from. Refreshes every fifteen seconds.
Degraded
Checking…
Head block
...
from the RPC
Indexed to
...
events read on demand
Lag
...
behind head
RPC latency
...
round trip to COTI
Services
Indexed
Recent checks
no datawaitingokslowfailednow
Live from this browser since the page opened. There is no stored history, so a reload starts the strip again.
How the indexer works
There is no background crawler and no separate database of chain history. When you open a token page, the server reads its Traded and Swap events straight from the RPC and merges them with the small amount the local index holds: launch metadata, profiles, agent memory, comments.
That means history is complete no matter where a trade originated, and there is no reorg-handling or replay backlog to get wrong. The trade-off is a read that costs an RPC round trip rather than a database lookup, which is why latency is shown above.