Developer Infrastructure · 9 min read

Arc block explorers and analytics tools: what tracks the chain, and how well

Block explorers and analytics platforms tracking Arc — testnet.arcscan.app, DefiLlama, Elliptic, Chainalysis, and more — status as of 2 Sep 2026.

The chain's own explorer is confirmed and testnet-scoped; the mainnet equivalent is not yet published; and third-party analytics coverage of Arc ranges from "actively tracking a live chain page" to "no confirmed coverage at all." This guide separates block explorers (which show you what happened on-chain) from analytics and compliance tooling (which interprets or monitors that data for a purpose), and reports what's actually verifiable for each, as of 2 September 2026.

Block explorer vs. analytics platform: not the same job

A block explorer is the base layer — a searchable interface over raw chain data: transactions, blocks, addresses, contract code. It answers "what happened," directly, with no interpretation layered on top. Arc's testnet explorer, testnet.arcscan.app, is confirmed and does this job for testnet activity today.

An analytics platform sits above that layer and does something with the data — aggregates it into dashboards, tracks fund flows for compliance purposes, ranks wallets by activity, or rolls protocol-level numbers (like TVL) into comparable metrics across chains. This is a fundamentally different function from an explorer, and a platform can do it well for one chain and not at all for another, independent of how good the underlying explorer is.

What's confirmed for the explorer layer

Arc's testnet explorer is live and confirmed at testnet.arcscan.app. The mainnet explorer URL was not published as of 2 Sep 2026 — the same gap that applies to mainnet RPC endpoints applies here, and for the same reason: mainnet doesn't exist yet. Any URL circulating before 16 September claiming to be "the Arc mainnet explorer" should be treated as unverified until Arc's own official channels confirm it.

What's confirmed for analytics and compliance tooling

These three (Elliptic, DefiLlama, Chainalysis) are Compliance & Analytics under Built on Arc's taxonomy, not Developer Infrastructure — see Compliance & Analytics for that category directly; the table above covers explorers only.

Elliptic has a confirmed, dated relationship: a press release (28 October 2025, the same day Arc's public testnet launched) states Elliptic joined as an infrastructure participant providing blockchain analytics for Arc's testnet, with Elliptic's CTO framing compliance infrastructure as foundational to the network rather than an add-on. This is explicitly scoped to testnet, with no mainnet commitment stated in the source.

Builds on Arc: Provides blockchain analytics and AML/sanctions screening for Arc, testnet-scoped since 28 Oct 2025. · Role: Serves · Category: Compliance & Analytics · Project page

DefiLlama currently maintains a live chain page for Arc (defillama.com/chain/arc), tracking DeFi TVL, fees, and revenue metrics for the chain in DefiLlama's standard format. This confirms DefiLlama has Arc listed and is tracking it as of 2 Sep 2026 — but any TVL, fee, or yield-dashboard interpretation of that data is explicitly ArcYield's territory, not this directory's. If you're looking for a read on Arc's actual TVL or yield landscape, go to ArcYield directly rather than treating this guide's mention of DefiLlama's existence as that analysis. (Not in the canonical role map — treat as a third-party analytics tool, Compliance & Analytics-adjacent, not a listed directory entry.)

Chainalysis is named directly in Circle's own Arc compliance-vendors documentation (docs.arc.io/arc/tools/compliance-vendors), alongside Elliptic and TRM Labs, as of 2 Sep 2026 — a correction to earlier reporting on this page, which had found no dated Arc-specific source and treated the relationship as unconfirmed. Circle's documentation names Chainalysis as a vendor for "transaction monitoring, address screening, and investigation tools"; it does not state a mainnet timeline or a specific coverage-live date, and no separate press release beyond the documentation listing was found. See Built on Arc's Chainalysis on Arc page for the full readout.

Builds on Arc: Provides transaction monitoring and address screening for Arc. · Role: Serves · Category: Compliance & Analytics · Project page

TRM Labs is named alongside Chainalysis and Elliptic on the same compliance-vendors documentation page, with no separate press release beyond that listing.

Builds on Arc: Provides wallet-screening and fraud-risk intelligence for Arc, including agent-payment flows. · Role: Serves · Category: Compliance & Analytics

Arkham, Nansen, and Dune — none of the three appears on Circle's compliance-vendors or any other named Arc documentation page, and no independently verifiable Arc-specific coverage, dashboard, or integration announcement was found for any of them as of 2 Sep 2026. All three are established analytics platforms with broad multi-chain coverage generally; none of that is evidence of specific, confirmed Arc coverage without a direct source, and none was found. Not yet confirmed for any of the three.

What an explorer needs to get right that's specific to Arc

A generic EVM block explorer forked or reused without Arc-specific work can get subtle things wrong that matter for this chain in particular: rendering gas correctly when gas is paid in USDC at 18 decimals rather than a conventional native gas token, correctly reflecting Arc's sub-second finality (roughly 780ms, per Malachite consensus) rather than assuming the longer confirmation windows most explorer UX was built around, and correctly labeling the permissioned validator set rather than displaying it with assumptions carried over from permissionless-chain explorer templates. None of this is independently verifiable for testnet.arcscan.app from published material as of 2 Sep 2026 — it is simply the list of things worth checking directly against the explorer itself, and worth re-checking against whatever explorer serves mainnet once one is published, rather than assumed correct by default.

Reading an analytics dashboard's numbers with the right skepticism

Any dashboard tracking Arc pre-mainnet — DefiLlama's chain page included — is by definition tracking testnet activity, because there is no mainnet activity yet to track. Testnet TVL, testnet transaction counts, and testnet wallet activity are not economically meaningful in the way the equivalent mainnet figures will be: testnet assets typically have no real market value backing them, and testnet activity is frequently driven by incentivized testing campaigns rather than organic usage. This guide will date-stamp any figure it cites from these platforms and will not present a testnet-era number as evidence of mainnet-scale adoption. That discipline is worth applying to any number you see cited from these dashboards elsewhere, too — a chain-page total looks the same whether the activity behind it is organic or a faucet-funded testing exercise.

The directory

From the directoryView all →
01BlockscoutAnnouncedServes2026-09-02
02Ormi LabsAnnouncedServes2026-09-02
03TenderlyAnnouncedServes2026-09-02
04The Crypto AppAnnouncedServes2026-09-02

Read this table with the explorer/analytics split in mind — a "confirmed" status for an analytics platform in this category means confirmed data coverage or a stated partnership, not confirmed accuracy or completeness of that coverage, which this guide has no way to independently audit.

Why the compliance-analytics angle matters specifically for Arc

Arc's positioning is institutional stablecoin infrastructure — payments, FX, capital markets — which puts transaction-monitoring and compliance analytics closer to core infrastructure for this chain than it would be for a general-purpose consumer chain. Elliptic's testnet-stage involvement, explicitly framed around compliance as foundational rather than optional, and Chainalysis's and TRM Labs' presence on Circle's own compliance-vendors documentation, are consistent with that positioning. Whether Arkham, Nansen, or Dune formalize an Arc-specific relationship before or shortly after mainnet is a reasonable thing to watch for, given the pattern — but it is not yet a confirmed fact as of 2 Sep 2026, and this guide will not present it as one.

What to watch for at mainnet

Three specific things to check once Arc mainnet launches 16 September: whether Arc publishes an official mainnet explorer URL (and where); whether DefiLlama's Arc chain page transitions from testnet-era to real mainnet TVL tracking; and whether Elliptic, or any other compliance-analytics provider, extends a testnet-scoped relationship into a stated mainnet commitment. None of these are answerable yet. For the RPC layer these tools query underneath, see Built on Arc's RPC providers comparison.

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

Sources: - Arc compliance vendors documentation - Elliptic provides Circle's Arc testnet with blockchain analytics - Arc - DeFi TVL, Fees, & Revenue - DefiLlama - Arc | The Economic OS — official site - Circle Launches Arc Public Testnet

Questions

Is there an official Arc mainnet block explorer?

Not yet — as of 2 Sep 2026, only the testnet explorer (testnet.arcscan.app) is confirmed and published. A mainnet explorer URL had not been published as of this date.

Does DefiLlama track Arc?

Yes — DefiLlama maintains a live chain page for Arc tracking TVL, fees, and revenue in its standard format. For interpretation of that data (what it means for yield, protocol comparison, or opportunity), see ArcYield rather than this directory.

Is Elliptic's Arc coverage live on mainnet?

No — Elliptic's confirmed involvement, per a dated 28 October 2025 announcement, is explicitly scoped to Arc's testnet, with no mainnet commitment stated in the source.

Does Chainalysis cover Arc?

Yes, per Circle's own Arc compliance-vendors documentation, which names Chainalysis alongside Elliptic and TRM Labs as of 2 Sep 2026. Do Nansen, Arkham, or Dune cover Arc? Not yet confirmed as of 2 Sep 2026 — none appears on Circle's documentation, and no independently verifiable Arc-specific coverage was found for any of the three.

Should I trust a site claiming to be "the Arc mainnet explorer" before 16 September?

No — Arc has not published one yet, so any such claim ahead of official confirmation should be treated as unverified.

Where do I find TVL or yield dashboards for Arc protocols?

That's ArcYield's job, not this directory's — see arcyield.app for TVL and yield-specific analysis.