SubQuery Indexer

WHAT IT DOES

SubQuery Indexer provides read-only access to your SubQuery project's indexed data. View project state, entity states, query results, schema state, block height, chain ID, gas price, and timestamps. This tool connects directly to SubQuery's GraphQL endpoint to fetch current indexing status and query results without submitting any transactions or making state changes.

HOW TO USE

1. Connect your Web3 wallet (Ethereum, Polygon, Arbitrum, or any EVM-compatible chain).

2. Select the network that matches your SubQuery project's deployment.

3. Enter your SubQuery project slug (the unique identifier for your indexer project).

4. Enter a lookup key — this can be an address, transaction hash, or token ID you want to query.

5. Click "look up" to retrieve indexed data from SubQuery's GraphQL API.

6. Review the results displayed in the results panel, including block height, chain ID, gas price, timestamp, and the specific entity state.

TECHNICAL MECHANISM

SubQuery Indexer works by sending GraphQL queries directly to the SubQuery service endpoint using the project slug you provide. The tool constructs queries based on your lookup key and the project's schema, then parses the JSON response to display structured data. Unlike simple block explorers that only show raw transaction data, this tool understands the entity relationships defined in your SubQuery project's schema — it can follow foreign keys, display nested entity states, and present query results exactly as your indexer processed them. When the lookup key is an address, the tool queries all entities where that address appears; for transaction hashes, it retrieves the block context and any derived entities. The tool automatically decodes common data types and formats timestamps, gas prices, and block heights for readability.

WHAT IT CANNOT SEE

This tool is a frontend for SubQuery data — it does not validate the indexing logic, verify data completeness, or audit the security of your SubQuery project. The tool cannot detect if your indexer project has been compromised, if the schema accurately reflects the actual data structure, or if the indexed data is fully up-to-date. It cannot predict future indexing performance or estimate when the indexer will catch up to the current chain head. All data is presented as provided by SubQuery — if your indexer project has gaps, errors, or stale data, this tool will display that information without warning. The tool does not verify that the schema matches the actual indexed data, and it cannot detect if the indexing logic has bugs that cause data omission or corruption.

PLEASE NOTE

SubQuery Indexer supports EVM-compatible blockchains only (Ethereum, Goerli, Polygon, Arbitrum, and others via network selection). The tool requires an active connection to your Web3 wallet for authentication and network detection, but never submits transactions or signs messages. All data is retrieved via public GraphQL endpoints — performance depends on the SubQuery service and your network connection. For projects with large datasets, query results may be truncated or paginated in future updates.