Retracer · In Development

Every block.
Every action. One query away.

Retracer watches Arxium and indexes everything that happens, so your app can ask “what did this account do” without replaying chain logic itself.

See the API Back to Ecosystem

retracer · ingestlive

✓ block 184211 · 7 actions indexed
✓ block 184212 · 12 actions indexed
✓ block 184213 · 9 actions indexed
▸ block 184214 · ingesting…

cursor  corechain-devnet @ 184213
lag     0 blocks behind tip

Interface

REST + gRPC

Data model

6 core tables

Coverage

Hub + every Spoke

Payloads

Any action shape

How it works

A pipeline, not a database dump.

Watch

Follows the network

Retracer sits behind the chain and sees every block and action the moment it lands.

Index

Keeps the record

Blocks, actions, and every address they touch — written down once, queryable forever.

Serve

Answers your queries

Account history, block ranges, free-text search — over plain REST or gRPC, no SDK required.

Data model

Six tables. The whole chain.

Reading history straight from a node means replaying blocks yourself just to answer “what did this account do.” Retracer ingests every block and action as it lands and keeps a queryable record, so your app doesn’t have to.

It’s the same data model that already backs the Explorer and Wallet inside Arxium, extended to run against any chain in the network — the Hub and every Spoke — from one deployment. A Spoke brings its own action types; Retracer indexes them without knowing their shape in advance.

Schema

blocksEvery block, in order.
actionsEvery action inside every block, as JSON — any payload shape.
account_actionsActions, indexed per account.
action_addressesEvery other role an action touches — recipient, validator, delegator.
chainsEvery chain this deployment follows, Hub and Spokes alike.
ingestion_cursorHow far Retracer has caught up, per chain.

The API

What a query looks like

Plain REST over the same data the Explorer and Wallet already query internally — no SDK, no schema to generate. The chain you’re asking about is always in the path, so one endpoint serves the Hub and every Spoke behind it.

retracer.api

GET /v1/chains/corechain-devnet/accounts/arx1q9f...2mk3/actions?role=to

[
  {
    "action_hash": "0x9f2a1c...e04b",
    "block_height": 184213,
    "kind": "Transfer",
    "from_address": "arx1p5k...9td2",
    "payload": { "to": "arx1q9f...2mk3", "amount": 500 }
  }, ...
]

Capabilities

Ask it anything that already happened

Block lookup

Fetch any block by height or hash, with every action inside it.

Account history

Every action a given address sent or received, newest first, paginated.

Free-text search

One query for a block height, an address, or a hash — no guessing input types.

Chain stats

Total blocks, block height, average block time, live tip.

Proposer history

Who has produced blocks, and how many, without touching validator state.

Multi-chain

Follow a Hub and its Spoke chains from one process, one query surface.

Coming Soon

Build on the chain’s memory.

Retracer is in active development and rolls out to builders on Arxium once it’s ready. Access will be announced here first.

Explore the Ecosystem

Every block.Every action. One query away.