Indexers and The Graph

Why Blockchains Need Indexers

Blockchains store transaction data in a form optimised for consensus and verification, not for querying. If you want to know 'how many NFTs did address X buy last week', 'what's the total volume on Uniswap yesterday', or 'which addresses hold token Y', you cannot get that from an RPC node in any reasonable amount of time. You need an indexer — a piece of infrastructure that reads every block, extracts the events and state changes you care about, and stores them in a queryable database. Almost every non-trivial dApp uses an indexer either operated in-house or a third-party service.

The Graph as the Category Leader

The Graph is the most widely used blockchain indexing protocol. It introduced the idea of a 'subgraph' — a small, declarative description of what data to index for a specific dApp, written by the dApp team and deployed to The Graph's indexer network. Once deployed, anyone can query that subgraph via GraphQL. Uniswap, Aave, Curve, Synthetix, and thousands of other protocols have subgraphs — often the same subgraph is used by the protocol's official interface and by dozens of third-party analytics tools.

Indexers Beyond The Graph

The Graph is not the only indexing option. Dune Analytics indexes chain data into SQL tables that anyone can query. Nansen, Arkham, and Chainalysis run proprietary indexers for their specific use cases. dApps that need lower latency or specific data shapes often build their own with tools like Ponder, Envio, or Subsquid. Big blockchains (Solana, Aptos, Sui) each have their own indexing ecosystems adapted to their specific data models. The category has fragmented as the industry has grown.

• Indexers translate raw chain data into queryable APIs
• Every non-trivial dApp uses one — in-house or a service
• The Graph is the largest general-purpose network
• Dune, Nansen, and various proprietary indexers serve different niches