Next generation EVM indexing
Instant access to the full history of every chain we run. Query blocks, logs, and traces raw, pipe them to your stack, or start from enriched datasets.
Live fleet metrics are temporarily unavailable.
Start at genesis, not at sync.
The full history is already in ClickHouse — every block, log, and trace, ordered and deduplicated. Your first query scans years; nobody waits for a node to catch up.
- Full depth from block one — no progressive backfills, no archive nodes to babysit.
- New blocks land beside the history, so one query spans genesis to head.
The whole chain, ready to query — genesis to head.
Still grinding through the backfill — and counting.
Keeps just the head — no deep history to index or analyze.
SQL over ClickHouse tables.
Query it the way you already know — standard SQL over the raw tables. Joins, aggregations, and window functions answer in seconds what RPC pagination answers in days.
- No proprietary query language, no rate limits — just columnar speed on indexed data.
-- Every USDC transfer since the contract deployed
SELECT
toStartOfMonth(timestamp) AS month,
count() AS transfers
FROM logs
WHERE chain = 1
AND address = unhex({usdc:String})
AND topic0 = unhex({transfer_sig:String})
GROUP BY month
ORDER BY month ASC| month | transfers |
|---|---|
| 2025-03-01 | 14,982,440 |
| 2025-04-01 | 16,103,887 |
| 2025-05-01 | 17,544,012 |
94 rows · 0.18 s
Skip the decoding.
Raw blocks are the foundation, but most questions start higher. Turtle ships curated datasets, queryable the moment you get access.
- Decoded, deduplicated, and normalized from the raw tables — no parsing to maintain.
- Tokens, transfers, and contracts today, with more landing regularly.
Same SQL, right beside the raw data — tell us what you need.
| symbol | name | decimals | address |
|---|---|---|---|
| USDC | USD Coin | 6 | 0xa0b8…eb48 |
| USDT | Tether USD | 6 | 0xdac1…1ec7 |
| WETH | Wrapped Ether | 18 | 0xc02a…6cc2 |
| WBTC | Wrapped BTC | 8 | 0x2260…c599 |
| DAI | Dai Stablecoin | 18 | 0x6b17…1d0f |
| LINK | Chainlink | 18 | 0x5149…86ca |
decoded · deduplicated · normalized
Pipe it anywhere.
Point a pipe at any slice of the data — raw logs, traces, or an enriched dataset — and Turtle delivers it to your infrastructure. Backfill years of history first, then stay at head.
Turtle pipesany source → any sinkOne pipe definition drives every destination. Shape the record once — pick the source, the fields, the batching — then replay history into a new system or fan the same stream out to several. The data and its ordering stay identical.
RPC at index speed.
One endpoint per chain, on every chain we run. eth_getLogs is answered from the same index that powers our SQL — typical reads clear in about 100 ms — instead of paginating an archive node. Every other method proxies through to healthy upstream nodes, on the same API keys as the data API.
The data is already there.
Genesis to head, ready to query — raw, piped, or enriched. Tell us what you're building.