Canonical: https://builtonarc.app/guides/arc-indexers-and-data-providers

# Indexers and data providers for Arc, mapped

Updated 2026-09-02. Envio, Goldsky, The Graph, thirdweb and Zerion document Arc data support. Dune, Covalent and Ponder don't, as of 2 Sep 2026. Here's the landscape.

> Circle's documentation names five data providers for Arc as of 2 September 2026: Envio, Goldsky, The Graph, thirdweb (Insight), and Zerion. Dune, Covalent, and Ponder do not appear on that list, and Built on Arc found no independent Arc-specific integration from any of the three. Arc's testnet block explorer, testnet.arcscan.app, is confirmed and live; no mainnet explorer has been published. Anything TVL- or yield-dashboard-shaped belongs to ArcYield, not this guide.

## Why indexing is its own layer, not part of RPC

Raw RPC access answers "what's the current state" one call at a time; an indexer answers "give me every transfer event matching this filter across the chain's history" without a team re-scanning blocks itself. On an EVM chain that's normally a GraphQL subgraph (The Graph, Goldsky) or a hosted event-indexing framework (Envio); on Arc specifically there's an added wrinkle documented in Circle's own EVM-differences reference — native USDC transfers emit `Transfer` logs from a system address in 18 decimals, separate from the ERC-20 contract's own 6-decimal `Transfer` events, which an indexer needs to de-duplicate deliberately rather than sum both.

## The five providers Circle documents

**Envio** — a "developer-first indexing framework for event-driven data and GraphQL APIs on Arc," with HyperIndex for rapid API deployment and live event streaming.

> **Builds on Arc:** Runs an event-driven indexing framework with a GraphQL API for Arc. · **Role:** Serves · **Category:** Developer Infrastructure → Indexing & explorers

**Goldsky** — managed subgraph services and data-pipeline infrastructure, with autoscaling query capacity and real-time streaming to external databases.

> **Builds on Arc:** Provides managed subgraphs and streaming data pipelines for Arc. · **Role:** Serves · **Category:** Developer Infrastructure → Indexing & explorers

**The Graph** — the decentralized subgraph protocol, querying Arc's onchain data with redundancy across independent indexers.

> **Builds on Arc:** Indexes Arc onchain data via decentralized, redundant subgraph queries. · **Role:** Serves · **Category:** Developer Infrastructure → Indexing & explorers

**thirdweb** — its Insight data API for retrieving and enriching Arc blockchain data; also independently documents Arc Testnet support (chain ID `5042002`, RPC endpoint, faucet) on its own site. Its canonical primary role in this directory is Account abstraction.

> **Builds on Arc:** Offers an Insight data API for retrieving Arc chain data. · **Role:** Serves · **Category:** Developer Infrastructure → Indexing & explorers

**Zerion** — portfolio and wallet data, covering balances, positions, and real-time wallet activity.

> **Builds on Arc:** Surfaces Arc wallet balances and portfolio positions via its data API. · **Role:** Serves · **Category:** Developer Infrastructure → Indexing & explorers

None of the five carries a mainnet-specific claim in the material Built on Arc reviewed — the entire indexing layer, like the rest of Arc's developer stack, is documented against testnet as of 2 Sep 2026.

## What's not on the list

Circle's data-provider documentation does not name **Dune**, **Covalent**, or **Ponder**, and none of the three had a public Arc-specific integration, blog post, or dashboard Built on Arc could source as of 2 Sep 2026. That is worth stating plainly rather than assuming: a chain being EVM-compatible does not automatically mean every general-purpose indexer has shipped support, and in Arc's case, three widely used ones evidently have not yet, at least not visibly.

## The explorer situation

Arc's testnet explorer, `testnet.arcscan.app`, is live and confirmed — it is the reference explorer named throughout Circle's own documentation. No mainnet explorer URL has been published as of 2 Sep 2026, which is consistent with the broader pattern covered in [/guides/arc-testnet-vs-mainnet-what-changes-for-builders](/guides/arc-testnet-vs-mainnet-what-changes-for-builders): Circle has not yet issued the mainnet-facing infrastructure values a team needs to point production tooling at.

## What this layer is not for

None of the providers above, nor Arc's testnet explorer, functions as a yield or TVL dashboard — that is a distinct product category, owned on the Built on Arc network by [ArcYield](https://arcyield.app/?utm_source=builtonarc&utm_medium=guide&utm_campaign=arc), which tracks protocol-level yield and TVL data across DeFi on Arc. A team building its own analytics on top of an indexer listed here is doing infrastructure work; a team looking for an existing yield dashboard should go straight to ArcYield rather than building one from a subgraph.

## Choosing between the five

This guide does not rank them, but the categories are genuinely different in shape: The Graph and Goldsky are subgraph-model services (schema-defined GraphQL over indexed events), Envio is positioned as a faster, more developer-controlled alternative in the same event-indexing space, thirdweb's Insight is a general-purpose data API rather than a custom-schema subgraph, and Zerion is specifically wallet/portfolio-shaped rather than general contract-event indexing. Which fits depends on whether the need is "query my own contract's events with a custom schema" (subgraph-model) or "show a user's balances and activity" (Zerion-shaped), not on which provider is "better."



Sources:
- [Arc data indexers](https://docs.arc.io/arc/tools/data-indexers.md)
- [Arc EVM differences reference](https://docs.arc.io/arc/references/evm-differences.md)
- [Arc connection reference](https://docs.arc.io/arc/references/connect-to-arc.md)
- [thirdweb: Arc Testnet](https://thirdweb.com/arc-testnet)

*Built on Arc is an independent directory. Arc is a Circle product; we are not affiliated with, endorsed by, or operated by Circle.*

## Questions

**Is testnet.arcscan.app Circle's own explorer or a third party's?**

Circle's documentation references it as the reference explorer for Arc Testnet; Built on Arc did not independently verify its operator identity beyond that it is the URL Circle's own docs point to.

**Can I use a generic EVM indexer that hasn't announced Arc support?**

Technically Arc is EVM-compatible, so generic tooling may work, but the EVM-differences documented by Circle (native-token transfer events, no base-fee burn) mean an indexer not specifically tested against Arc could double-count or mis-handle those cases. Treat unannounced compatibility as unverified, not assumed-working.

**Does The Graph's decentralized network already have live Arc subgraphs?**

Circle's documentation confirms The Graph as a supported data provider for Arc; Built on Arc did not verify the count or maturity of live third-party subgraphs already deployed, which is a separate question from platform support existing.

**Where do I find TVL or yield data for Arc protocols?**

That's ArcYield's remit, not an indexer question — see arcyield.app.

**Will Dune or Covalent add Arc support before mainnet?**

Built on Arc does not speculate on unannounced roadmaps. Neither had confirmed Arc support as of 2 Sep 2026.
