subgraph-development-guide

To build a subgraph, define your schema.graphql entities, wire event-driven mapping handlers in AssemblyScript, and configure target contract data sources in subgraph.yaml to expose a queryable GraphQL API.

The best way to track token transfers for DeFi analytics is using a subgraph to convert on-chain events into structured entities, enabling efficient historical aggregation and queryable derived relationships between accounts and tokens.

Yes, The Graph supports indexing DEX swap events by defining event handlers in your subgraph manifest, allowing you to model swap volume trends and token metadata relationships for analytics dashboards via GraphQL.

You query recent large transfers and top token volumes by executing GraphQL queries against your subgraph endpoint, retrieving filtered and sorted event-derived entities based on the schema relationships you defined.

Yes, you need AssemblyScript to write mapping handlers for a subgraph, as it is the language used to process event-driven blockchain data and store it as entities defined in your GraphQL schema.

Querying blockchain data directly is slow because it lacks aggregation and relationships; a subgraph solves this by indexing on-chain events into a structured GraphQL API for fast, queryable analytics.