Arc network statistics

This page tracks how much activity Arc actually carries, refreshed weekly, and explains what each figure measures and where to read it live yourself. Every number carries the date it was measured and the source it came from, because a network statistic without a date and a source is decoration. For which applications run on Arc rather than how much volume the chain moves, see [/arc/ecosystem](/arc/ecosystem).

This page covers Arc in its first weeks of mainnet. Arc went live on September 16, 2026, so the figures below are a short and volatile series rather than a trend, and we would rather show you an empty cell with a stated methodology than a number we cannot source. Last reviewed: September 2026.

First published: September 2026. The table cells below are populated at each weekly refresh, every Monday, with the measurement date recorded alongside each figure. A cell showing an em dash has not been measured for the current week.

What are Arc's current network statistics?

Arc is Circle's Layer-1 for stablecoin settlement, live on public mainnet since September 16, 2026, with gas paid in USDC and deterministic finality of roughly 780 milliseconds. The pre-mainnet baseline was about 13.5 million weekly transactions on public testnet as of mid-August 2026, at an average fee of roughly $0.004 per transaction — a baseline for orientation rather than a proxy for economic activity, because testnet value is free.

The tables below hold the weekly figures. The prose after them says what each metric measures, where to read it live, and how it is commonly misread, which is the part that stays true between refreshes.

Network activity

Measured from the Arc block explorer over a rolling seven-day window.

Value on the chain

Measured in US dollars. The DeFi aggregator used is named in the cell at each refresh, because aggregators disagree.

Cost and performance

The baseline column carries the last figure we can source; the current column is measured on mainnet at each refresh.

Validators and decentralisation

The eleven founding validators are BlackRock, DTCC, Galaxy, Global Payments, ICE, Mastercard, MoneyGram, SBI Group, Standard Chartered, Sumitomo and Visa. Why that composition matters is covered at /arc/validators.

How is each metric defined and where does it come from?

Transaction counts are raw counts of included transactions from the block explorer, not deduplicated by sender and not filtered for spam or self-transfers. A count measures chain usage, not economic activity, and one application looping transactions can move it a long way. Read them from the explorer's chart or analytics view rather than from a third-party dashboard, since the explorer is the source those dashboards derive from; /arc/arcscan-guide covers navigating it.

Total value locked is the aggregate USD value of assets deposited in DeFi protocols on Arc, as reported by third-party aggregators. It is the most quoted chain statistic and the most misread. TVL counts the same dollar twice when an asset is deposited, borrowed against and redeposited; it moves with prices rather than with user behaviour; and aggregators apply different inclusion rules, so two sources disagree and both can be right. Always name the aggregator, which is why the table names it in the cell rather than in a footnote.

USDC supply on Arc is the amount of USDC issued on the chain, readable from the USDC token contract's total supply on the explorer. It is more meaningful here than on most networks, because USDC is the gas asset as well as the settlement asset, so supply tracks willingness to hold funds on the chain rather than a bridge's inventory.

Active addresses counts distinct addresses that sent at least one transaction in the window. It is a weak proxy for users: one person can hold many addresses, and one custodial address can represent many people.

Average transaction fee is the mean USD cost of a transaction over the window. Arc charges gas in USDC at 18 decimals, removing the usual step of converting a native-token fee at a fluctuating price. Fees vary by complexity: a plain transfer and a contract interaction are not comparable, which is why the median is tracked alongside the mean. /arc/gas-fees explains how fees are constructed.

Block time and finality are distinct. Block time is how often blocks are produced; finality is when a block can no longer be reverted. Arc uses Malachite consensus with deterministic sub-second finality of roughly 780 milliseconds, so a settled transaction is settled rather than probably settled. Finality is a protocol property from Circle's documentation and does not change week to week; block time is measured.

How can you check these numbers yourself?

Every figure here is reproducible from public sources: counts and charts from the block explorer, raw values from any RPC endpoint. Circle has not yet published Arc's mainnet chain ID, RPC endpoint or explorer URL, so the commands below carry MAINNET-TBD where the endpoint belongs — substitute Circle's published mainnet RPC endpoint before running them, and take it from Circle's own documentation rather than a third-party list.

# Substitute Circle's published mainnet RPC endpoint for MAINNET-TBD.
export ARC_RPC=MAINNET-TBD

# Current block height
cast block-number --rpc-url $ARC_RPC

# Transaction count in the latest block
cast block latest --rpc-url $ARC_RPC --json | jq '.transactions | length'

# Current base fee, denominated in USDC at 18 decimals
cast base-fee --rpc-url $ARC_RPC

Sampling block height twice a minute apart and dividing gives you a block time you measured rather than one you read. Testnet remains queryable at chain ID 5042002 via rpc.testnet.arc.io, explorer testnet.arcscan.app, faucet faucet.circle.com. Testnet figures are useful for orientation and useless as a proxy for economic activity. /arc/mainnet-vs-testnet sets out the distinction.

How should you read a chain's statistics honestly?

Read them against each other. A rising transaction count with a flat address count usually means existing users doing more, or one application generating volume. Rising TVL with flat transfer volume means capital is arriving but not being used. Rising fees usually mean congestion; on Arc, where fees are quoted in USDC, a rising average more often means the transaction mix has shifted toward heavier contract calls.

Treat the first months of any new chain's figures as noisy. Launch incentives, migration flows and one-off deployments distort early data in both directions, and week-over-week change carries more information than any single week's level. That is the honest reason this page shows its methodology as prominently as its numbers: in a chain's opening weeks the methodology is the more durable half.

Refresh procedure

Refreshed every Monday. Pull the seven-day transaction count, daily average, cumulative count, active and new addresses from the block explorer; TVL from the named aggregator; USDC supply and transfer volume; average and median fee, block time and the active validator count. Move last week's figures into the "previous week" column, record the measurement date against each, update the stamp at the top, and note any methodology change inline rather than silently. A metric that could not be sourced this week goes back to an em dash rather than carrying last week's number forward.

What is Arc's TVL right now?

TVL on Arc is the aggregate USD value of assets deposited in DeFi protocols on the chain, measured by third-party aggregators whose inclusion rules differ, so the figure is only meaningful quoted alongside the aggregator that produced it and the date it was read. The current figure and its source are in the "value on the chain" table above, refreshed each Monday.

How many transactions does Arc process?

Arc's mainnet transaction counts for the current and prior seven-day windows are in the "network activity" table above, taken from the block explorer and refreshed each Monday. For a pre-launch reference point, Arc's public testnet carried roughly 13.5 million transactions per week as of mid-August 2026, before mainnet launched on September 16, 2026.

What does a transaction cost on Arc?

Fees are paid in USDC rather than a volatile native token, which is why an Arc fee is quotable in cents without a price lookup. Arc's testnet averaged about $0.004 per transaction as of August 2026. The current mainnet average and median, with the date each was measured, are in the "cost and performance" table above.

How often is this page updated?

Weekly, every Monday, with the previous week's figures retained for comparison and the refresh stamp at the top of the page. A cell showing an em dash means that metric has not been measured for the current week rather than that it is zero.

Why do different sites report different TVL for Arc?

Because aggregators define TVL differently: which protocols are included, whether staked and restaked positions count once or twice, whether idle bridged assets count at all, and at what price assets are marked. There is no single correct figure, only figures with stated methodologies. Compare like with like, or compare direction rather than level.