A November 4, 2026 overview of The Graph’s subgraphs maps out a practical boundary: an EVM subgraph can index selected on-chain activity and state, but it is not a complete record of everything a chain executes.
Start with events. Event handlers are the main and most reliable route described in the overview. They can index emitted contract events alongside transaction and block metadata. For data a contract does not emit, a mapping can use eth_call to read contract state. That read reflects state at the block level and requires an archive node that supports EIP-1898.
Use other handlers for specific gaps. A call handler can follow contract function calls that emit no event, but it depends on trace_filter, which many networks and RPC providers do not offer. A block handler can sample state every block or at a fixed interval. Neither turns a standard subgraph into a full execution-trace index.
Full execution traces, internal transfers, pending transactions and a chain’s complete transaction history fall outside standard subgraph capabilities. The overview points to debug_traceTransaction, Substreams or a custom indexing pipeline for those needs. It also distinguishes querying historical entities stored by a subgraph from reading historical state on-chain, and notes isolation limits for IPFS and Arweave file data sources.
For someone choosing an indexing approach, the source’s sequence is straightforward: check whether events contain the needed data first; then consider state reads or call and block handlers; turn to tracing or chain-wide indexing only when those narrower options are insufficient. The availability of the required node and RPC features remains part of that decision.