Decentradge
Menu

What an EVM Subgraph Can—and Cannot—Index

A November 4, 2026 overview of The Graph’s EVM subgraphs draws a practical boundary: subgraphs can index selected on-chain data, but they are not a complete record of chain execution.

Start with events. Event handlers are the main, most reliable approach described in the overview. They can also capture transaction and block metadata. When events are insufficient, a mapping can use eth_call to read contract state, but that returns state at the block level and requires an archive node that supports EIP-1898.

Other handlers cover narrower needs. Call handlers can track contract function calls that emit no event, but depend on trace_filter, which many networks and RPC providers do not offer. Block handlers can sample state at every block or at a fixed interval.

The overview places full execution traces, internal transfers, pending transactions and chain-wide transaction history outside standard subgraph capabilities. Those needs call for tools such as debug_traceTransaction, Substreams or a custom indexing pipeline. It also distinguishes querying the history of subgraph entities from reading historical on-chain state, and notes isolation limits for IPFS and Arweave file data sources.

The suggested selection order is to check events first, then consider state reads and call or block handlers, and turn to tracing or chain-wide indexing only when those approaches do not cover the required data.

Further reading