Query Decoded Chain Data

Tessellate Indexing turns EVM chain data into tables you can query with SQL or GraphQL, using your own ABI mappings.

Why Use Tessellate Indexing

Indexing chain data well is hard. Teams run nodes, write decoders, handle reorgs and backfill history before they can ask a single question. Tessellate runs that pipeline for you and serves the decoded events and traces you define, with reorg handling built in.

Use Cases

Power product analytics:

Querydecoded events in SQL to feed dashboards, reports and in-app views without running your own pipeline.

Monitor protocol activity:

Use traces and events from your contracts to track usage, flows and invariants over time.

Support audits and incident review

Replay history from Redpanda to reconstruct what happened, and alert when a contract invariant is violated.

The Indexing Pipeline

Tessellate Reth ExEx Ingestion

Tessellate Decode and Store

A Reth execution extension streams canonical blocks, with reorg notifications, into a Rust ingestion service. A decoder applies your ABI mapping and writes to Redpanda, which supports replay and backfill.

ClickHouse stores append-only events and traces. Postgres holds mutable entity state. You query both through SQL or GraphQL, with materialised views for the aggregates you need.

The pipeline is configured declaratively, and you control the shape of your data. At launch this includes:

Reorg Window

Data inside the reorg window (64 blocks on Ethereum) is served with finalised:false and rewritten if the chain reorganises.

Freshness

Head-to-queryable target of p95 under 3 s on Ethereum and under 2 s on OP Stack chains.

ABI Mappings

Declarative ABI mappings and SQL materialised views at launch. Sandboxed TypeScript handlers are planned for month eight.

Query Limits

30 s query timeout, 100,000 rows per response and 10 concurrent queries on Scale.

Backfill

Historical backfill runs at about 50 million events per hour, so large contracts take hours rather than weeks.

Scope

EVM chains only. There are no cross-chain joins and no non-EVM data.

How Indexing Is Delivered

Indexed data is available through three interfaces, and replay is available from Redpanda for backfills:

decoded events
runs read-only SQL over ClickHouse and Postgres with a 30 s timeout and a 100,000 row response cap.

GraphQL
exposes your entities and relations as a typed schema generated from your ABI mapping.

Replay
re-reads decoded events from a chosen block so you can rebuild a table after changing a mapping.

Tessellate Advantages

Reorg-Aware Data
Every row says whether it is finalised, and rows are rewritten if the chain reorganises.

Less to Operate
No decoder service, queue or database cluster to run. Plans start at A$149 a month.

One Stack
Indexing shares the same Reth nodes and status page as Tessellate RPC.

Meet with us

Bring reliable infrastructure to your organisation

Tessellate respects your privacy. By submitting this form, you are acknowledging that you have read and agree to ourPrivacy Policy, which details how we collect and use your information.