Data coverage
Arcscan indexes Arc mainnet and Arc testnet separately, and neither index covers everything — this page states which block ranges exist, which capabilities each chain has, and what you see when you ask for something outside them.
What is indexed, per chain#
Coverage is tracked as independent streams. chain is blocks, transactions and receipts; balances is token and native balances and the holder lists built from them; traces is execution traces swept and stored for whole ranges of blocks. A stream can sit behind the others, and one of them is empty on both chains.
Every figure in the two tables below was read from /v1/chain on 2026-08-10. For today’s, read Node status, which publishes the same fields live.
Mainnet (chain 5042)#
| Stream | From block | To block | Ranges | Contiguous |
|---|---|---|---|---|
| balances | 0 | 14,852,047 | 1 | yes, from block 0 |
| chain | 0 | 14,852,093 | 1 | yes, from block 0 |
| traces | none | none | 0 | nothing indexed |
Mainnet is contiguous from genesis: one unbroken range per populated stream, so there are no holes to declare. At the moment of the reading the chain head was block 14,852,081 and the chain stream stood at 14,852,093.
Testnet (chain 5042002)#
| Stream | From block | To block | Ranges | Contiguous |
|---|---|---|---|---|
| balances | 53,500,000 | 56,246,685 | 1 | yes, from block 53,500,000 |
| chain | 53,500,000 | 56,246,687 | 1 | yes, from block 53,500,000 |
| traces | none | none | 0 | nothing indexed |
Testnet is contiguous too, but it does not start at genesis — see the next section. 2,746,688 blocks of chain and 2,746,686 of balances were held at the reading.
trace is available; the traces stream is empty
Both chains report thetrace capability as true, and on both chains the traces stream holds 0 blocks in 0 ranges. Those answer two different questions. Internal transactions for a transaction you name are available on both chains; a query across a range of blocks by trace is not, because there is no indexed range to query. When that changes it will change here — we are not going to guess at a date.Testnet history starts at 53,500,000#
Arcscan’s testnet index begins at block 53,500,000, not at the chain’s first block. The 53,500,000 blocks below that point were never indexed here, so no Arcscan page, API route or search can answer for them: a testnet block, transaction or transfer that exists only down there will not be found on this site.
An empty result below block 53,500,000 is our gap, not the chain’s
/v1/chain says this itself, in the field a client is meant to show a reader: “The 53,500,000 blocks below that point are not indexed here at all, so no Arcscan surface can answer for them: an empty result for that range is Arcscan’s missing history, not the chain’s.” Testnet coverage is therefore reported as incomplete — deliberately, and it stays that way while the floor is where it is.Mainnet has no such floor. Its chain and balances streams both start at block 0, and mainnet coverage is reported as complete.
Capabilities, per chain#
These are the flags /v1/chain publishes for each deployment. 4 of the 9 differ between the two chains, so a feature you found on testnet.arc-scan.ioOpens in a new tab is not evidence that it exists on mainnet, or the other way round.
| Capability | Mainnet 5042 | Testnet 5042002 |
|---|---|---|
| tx_index | yes | yes |
| holder_index | yes | yes |
| internal_transactions | yes | yes |
| trace | yes | yes |
| ots_search | no | no |
| archive | yes | no — state at a past block cannot be read |
| debug | no | yes |
| ots | no | yes |
| verified_source | no — not possible on this chain today | yes, for what has been cached |
The asymmetry is not an oversight in either direction: mainnet has the archive depth, testnet has debug and the Otterscan endpoints — though not their search, which is off on both chains. Where a capability is off, the surfaces that would depend on it are absent rather than empty.
Contract source#
This is the row that surprises people, so it is worth quoting. On mainnet verified_source is false, and the reason is upstream of us:
From /v1/chain, chain 5042
“Sourcify does not list chain 5042, so no contract on this chain can be verified today — through Arcscan or through any other client of Sourcify. Nothing here is waiting on Arcscan; it is waiting on the chain being added upstream.”So these docs will not tell you how to verify a mainnet contract: there is no way to do it, here or anywhere. On testnet Sourcify does list 5042002 and verified source can be published — but what Arcscan holds is a cache, filled the first time somebody asks for a given contract. The number of testnet contracts Arcscan has source for is a cache size, and it is far smaller than the number that are verified.
Absent, never zero#
An explorer’s only product is being believed, so one rule outranks completeness here: a value that could not be fetched is left out of the page, never filled in with a zero. Zero is a measurement. A blank, or a sentence saying what is missing, is the truth.
In practice:
- A block whose body can no longer be retrieved reads unknown, not zero — never “0 transactions”, which would be a claim about the block rather than about us.
- A reverted transaction is never rendered as a successful one, whatever a partial receipt might imply.
- A figure that depends on a capability the chain does not have, or on a stream that has not reached the block you asked about, is omitted with a reason rather than shown as nothing-happened.
The first two have regression tests behind them. If you ever see a value on this site that looks like a placeholder, treat it as a bug worth reporting rather than as data.
These numbers move#
Every figure above is a reading taken on 2026-08-10, and the upper bounds went stale immediately: mainnet’s chain stream advanced 59 blocks between two fetches about 4 minutes apart while this page was being written. That is what a 506 ms block time does to a number typed into a document.
What does not move is the shape — the floors (0 on mainnet, 53,500,000 on testnet), the fact that each populated stream is a single contiguous range, and the capability matrix. For a current upper bound read Node status, or fetch it yourself:
# the two documents every figure on this page was read from curl -s https://api.arc-scan.io/v1/chain # chain 5042 curl -s https://api-testnet.arc-scan.io/v1/chain # chain 5042002
If a number on this page disagrees with /v1/chain, the API is right and this page is out of date.