Arc Blockchain API
Bitquery’s Arc Blockchain API queries and streams data from Circle’s Arc blockchain (chain ID 5042). Use Trading for trading queries and streams, with Pair.Market.Network: "Arc" on Trading.Trades. Use EVM(network: arc) for transfers, balances, logs, calls, transactions and blocks.
Use Trading.Trades, Trading.Tokens and Trading.Pairs for live data and the last 30 days. Use EVM.DEXTrades or EVM.DEXTradeByTokens only for trades older than 30 days, subject to Arc archive availability.
Arc is Circle's EVM-compatible Layer 1. USDC pays gas, blocks reach finality in under a second, and the network is built for payments, foreign exchange and tokenized assets. Arc launched on 16 September 2026. Circle's current RPC reference still labels its listed Arc endpoints and explorer as permissioned; Bitquery's indexed API is live.
Trading.Trades, Trading.Tokens, Trading.Pairs, and the realtime EVM cubes returned Arc data in production tests. Leave the dataset argument out of Trading; it does not support archive or combined. Arc's EVM dataset: combined and dataset: archive did not answer at this check.
To query or stream outside the Bitquery IDE, create an API access token.
Arc at a glance
| Property | Value |
|---|---|
| Trading network | Arc in Pair.Market.Network for trades; Market.Network for pair candles; Token.Network for token candles |
| EVM network | arc in EVM(network: arc) for other chain data |
| Chain ID | 5042 |
| Gas token | USDC, tracked as Currency.Native: true |
| USDC ERC-20 interface | 0x3600000000000000000000000000000000000000 (6 decimals) |
| EURC | 0xbEf5f6d51CB62b58e6A8f77868681825C6fe21c1 (6 decimals) |
| USYC | 0x8a5D989Bbb96929F689B0200f435f53dA42bF490 (6 decimals) |
| Uniswap v4 PoolManager seen by Bitquery | 0x8366a39cc670b4001a1121b8f6a443a643e40951 |
| Arc explorer | explorer.arc.io (listed as permissioned in Arc's RPC reference) |
| Arc RPC | https://rpc.mainnet.arc.io (listed as permissioned in Arc's RPC reference) |
| Bitquery GraphQL | https://streaming.bitquery.io/graphql |
Arc's network reference confirms chain ID 5042, USDC as the currency symbol, the RPC and the explorer. Arc's contract list gives the stablecoin addresses.
Quick start: latest Arc swaps
This Trading query returns the newest Arc trade rows with USD amounts and the market name.
▶️ Run in IDE
{
Trading {
Trades(
limit: {count: 10}
orderBy: {descending: Block_Time}
where: {Pair: {Market: {Network: {is: "Arc"}}}}
) {
Block { Time }
TransactionHeader { Hash }
Trader { Address }
Side
Amounts { Base Quote }
AmountsInUsd { Quote }
PriceInUsd
Pair {
Market { Network Protocol }
Token { Id Symbol }
QuoteToken { Id Symbol }
}
}
}
}
Change query to subscription and remove limit and orderBy for a live feed. Follow WebSocket authentication to connect. See the Arc trades guide for token, pool, trader and protocol filters.
Pick the right API
| What you need | Cube | Guide |
|---|---|---|
| Recent trades, USD volume and traders | Trading.Trades | DEX Trades API |
| Recent token prices and OHLCV | Trading.Tokens, Trading.Pairs | Prices and candles |
| Trades older than 30 days, once Arc archive is available | EVM.DEXTrades, EVM.DEXTradeByTokens | Older history |
| New tokens from verified launchpads, then their first trades | EVM.Events, then Trading.Trades | Launchpads API |
| Argus decoded launches, dev buys, launch calls, token trades and OHLCV | Events, Calls, Trading.Trades, Trading.Pairs, Trading.Tokens | Argus Launchpad API |
| Tolly launches, token trades, trader rankings and OHLCV | Events, Trading.Trades, Trading.Pairs, Trading.Tokens | Tolly Launchpad API |
| RadarDEX Classic and Reflection launches, trades and prices | Events, Trading.Trades, Trading.Pairs, Trading.Tokens | RadarDEX Launchpad API |
| Minara launches, pool creators, trades and OHLCV | Events, Trading.Trades, Trading.Pairs, Trading.Tokens | Minara Launchpad API |
| Token and native USDC movement | Transfers | Transfers API |
| Decoded logs and new pool events | Events | Events API |
| Method calls, call trees and reverts | Calls | Calls API |
| Transactions, receipts, blocks and fees | Transactions, Blocks | Transactions API |
| Portfolios, holders, balance history and supply | Balances, Holders, TransactionBalances | Balances API |
USDC on Arc
Native USDC and the ERC-20 interface share Arc's USDC model, but Bitquery exposes separate rows so each source stays clear.
| Form | Bitquery fields | Decimals |
|---|---|---|
| Native USDC | Token.Id: "bid:arc" and empty Token.Address in Trading; Currency.Native: true, SmartContract: "0x" in EVM transfers and balances | 18 |
| ERC-20 USDC | SmartContract: "0x3600000000000000000000000000000000000000" | 6 |
| System ledger mirror | 0xfffffffffffffffffffffffffffffffffffffffe, no symbol | raw integer |
Filter on Native: true for gas-token value transfers. Use the 0x3600... address for ERC-20 calls and transfers. Exclude the system ledger mirror from token rankings.
DEX data on launch day
Production checks found active Uniswap v4, v3 and v2 markets. Use Trading.Trades with Pair.Market.Network: "Arc" for these trades. The feed can include NFT market fills; filter Pair.Market.Protocol or Pair.Market.ProtocolFamily when you need a specific swap venue.
Arc token IDs use bid:arc:<contract>, and native USDC uses bid:arc. To inspect a trade's calls, logs or transfers, take TransactionHeader.Hash and query the matching EVM cube separately.
Datasets and history
Trading serves live data and a rolling window of about 30 days. Arc may have less history while indexing starts. Only use the EVM trade cubes for older trades, after archive support is confirmed.
On 16 September 2026, only Arc's realtime EVM path answered. The following check measures EVM block history; it does not measure the Trading window:
▶️ Run in IDE
{
EVM(network: arc) {
Blocks {
count
earliest: Block {
Number(minimum: Block_Number)
Time(minimum: Block_Time)
}
latest: Block {
Number(maximum: Block_Number)
Time(maximum: Block_Time)
}
}
}
}
dataset: combined returned an unavailable-data error and dataset: archive could not reach its backing host during the check. Retry before treating those modes as live.
Real-time streams
Use Trading.Trades for trade streams and Trading.Tokens or Trading.Pairs for price and candle streams. Change the operation to subscription and drop limit, orderBy, and historical time filters. Keep token and trader leaderboards built with aggregates such as count or sum as HTTP queries; see streaming limits. The Ranking.Position filter on the candle cubes can still be used in a subscription.
See WebSocket subscriptions and WebSocket authorization.
FAQ
What is the Bitquery network name for Arc?
Use Arc in Pair.Market.Network for Trading.Trades. For other chain data use EVM(network: arc). The chain ID is 5042.
Are USD fields available?
Yes. Trading.Trades returns PriceInUsd and AmountsInUsd.Quote. Trading.Tokens and Trading.Pairs return USD candles and Volume.Usd. Field names differ from those on the EVM cubes.
How far back does Arc data go?
Trading has a rolling window of about 30 days; Arc may have less history while indexing starts. Arc's realtime EVM dataset was live at launch, but combined and archive were not ready during the 16 September check. See datasets and history.
Can I use Trading.Trades for Arc?
Yes. It is the default for Arc trade streams and trades within the last 30 days. Filter Pair.Market.Network by Arc. Use EVM trade cubes only for older trades, subject to archive availability.
Does Bitquery provide Arc RPC access?
No. Bitquery is an indexed data API. Use Arc's RPC for state calls and transaction submission; use Bitquery for indexed queries and streams.
Ready to run this in production?
Get an API key and run these queries in minutes, or talk to us about plans and enterprise delivery.