dton

dton (dton.io) is an independent indexer and GraphQL explorer for TON. Functionally it sits closest to BigQuery over a blockchain: nodes fold the full history of transactions, jetton operations and NFT events into a relational store, on top of which a GraphQL and SQL API runs. That data backs dashboards, academic research and dApp backend analytics.

How it differs from a lite server

A TON lite server only retains the latest blocks and the current account state. It cannot answer queries like “give me every transfer event of the USDT jetton master in April” — there is no historical index. Toncenter and TonAPI return paginated account history, but folding “stats across all holders of jetton X” through them becomes a chain of thousands of requests. dton solves both: a single GraphQL query returns the aggregate for the chosen window.

What it can do

• Transactions and messages — filter by op, src, dst, time.
• Jetton data — every wallet contract for a given master, turnover, top holders.
• NFT events — Getgems sales, transfer events, the history of a single item.
• Get-method snapshots — the indexer polls popular get-methods on a schedule and stores the answers so you can query past values.
• Cross-shard search — the indexer merges the masterchain and shards into a shared table; no manual stitching.

Pricing and keys

The base GraphQL endpoint is public with a rate limit. Production workloads use a paid plan with an API key and lifted limits. For heavy analytical loads you can run dton yourself — the team publishes the indexer and the schema on GitHub.

When to pick dton

• A dashboard with historical charts — TVL, turnover, active addresses.
• An analytical report “top 100 jettons by turnover this quarter”.
• Anomaly search: “find every transfer over 100k TON from a single address in the past month”.

For “read a balance or NFT metadata right now” dton is overkill — that is what TonAPI or Toncenter are for. dton is the historical-slice tool, not the real-time one.