Subgraph Sync Status Monitor
Free to download on every platform. Comes pre-installed on BotFone, BotPad and BotFlip — with extra free apps included.
About this app
WHAT IT DOES
Subgraph Sync Status Monitor is a read-only developer tool that monitors the synchronization progress of The Graph subgraphs against EVM chain heads. It queries the subgraph's GraphQL endpoint for the _meta status field, retrieves the latest synced block and chain head block, calculates sync progress percentage, and displays health status information. The tool optionally compares the subgraph's synced block against the current chain block (retrieved via ethers.js) to validate sync accuracy. It provides a comprehensive dashboard including subgraph name, sync status (synced/syncing/failed), health (healthy/unhealthy), synced block number, chain head, progress bar, entity counts, deployment ID, and version information—helping developers verify that their subgraph is properly indexing contract events before relying on it for dApp data.
HOW TO USE
Connect your EVM-compatible wallet via the BGWallet bridge and select the network matching your subgraph. Enter the subgraph query URL (e.g., https://api.thegraph.com/subgraphs/name/owner/subgraph) and optionally provide the contract address for chain head comparison. Click "Check Sync Status" to query the subgraph's _meta field and fetch the current chain block. Results include sync progress percentage, status indicators, entity counts, and a visual progress bar. The tool is ideal for pre-deployment verification and ongoing monitoring of subgraph health. All analysis is read-only—no signatures or transactions are submitted.
TECHNICAL MECHANISM
The tool uses ethers.js v5.7.2 to fetch the current block number from the EVM chain via provider.getBlockNumber(). It then constructs a GraphQL query targeting the subgraph's built-in _meta field, which is available on all subgraphs hosted on The Graph network and typically includes hasIndexingErrors, block, and deployment information. For subgraphs that support the standard _meta query, the tool retrieves the block number, block hash, and deployment ID. The tool parses the response to extract the latest indexed block, compares it with the current chain head, and calculates the sync progress percentage. Entity counts are approximated by running a simple GraphQL count query on commonly indexed entities (Transfer, Approval, etc.) when available. The tool also attempts to parse the subgraph name from the URL path and displays it for context. If the contract address is provided, the tool verifies it's a contract using getCode before fetching the chain block. All results are presented in a formatted dashboard with status tags, progress bars, and summary statistics.
WHAT IT CANNOT SEE
This tool has fundamental limitations that users must understand. It cannot directly interact with the subgraph deployment infrastructure—the tool only reads public GraphQL endpoints and cannot trigger re-syncs, restart indexing, or modify deployment settings. It cannot trigger or restart sync processes—if a subgraph is stalled, the tool cannot restart it. It cannot guarantee subgraph availability or query response times—public endpoints may be rate-limited, unavailable, or slow. It cannot monitor subgraphs that are not publicly accessible—private subgraphs or those behind firewalls require additional configuration not supported by the tool. It cannot detect indexing failures without Graph Node API access—some failures are only visible through the Graph Node's internal API, not the public GraphQL endpoint. It cannot monitor subgraphs deployed to private networks without configuration—the tool relies on a default connection to the selected EVM network. It cannot analyze subgraph data quality or query performance beyond basic sync status. It cannot detect schema mismatches or event handler bugs that would cause incomplete indexing. The tool's entity counts are approximated and may not reflect all indexed entities.
PLEASE NOTE
This tool only supports EVM-compatible blockchains (Ethereum, Polygon, BSC, Avalanche C-Chain, Optimism, Arbitrum, and their testnets). Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported. The tool is free, open-source, requires no API keys, and uses the wallet's native provider for all read operations. Subgraph sync status may vary depending on the Graph Node configuration and network conditions.