Addresses that have proposed at least one block. Arc runs Malachite BFT over a rotating proposer set, so this list is the validator set itself — read off block headers, not crawled.
Execution-layer entities exposed at fixed addresses: the native USDC mirror emitter, the ERC-20 face of the gas token, and the Arc precompile family.
Contracts that have emitted at least one Transfer event.
Fungible token contracts.
Non-fungible token contracts.
Multi-token contracts. Present on Arc but rare — one TransferSingle in 300 sampled blocks.
Every address Arcscan has seen come into existence via CREATE or CREATE2.
Addresses that have deployed at least one contract.
Contracts whose published source has been compiled and matched against the bytecode deployed on chain. Verification is opt-in — a contract earns this label when somebody submits its source, so an unverified contract is not a suspicious one, only an unexamined one.
Addresses with no known private key that funds are sent to in order to destroy them.
Every address Arcscan has identified, with the evidence for each. Names come from a factory relationship, a string in the contract's own deployed bytecode, a block header, or the execution layer itself — never from a guess.
Where these labels come from
Most groups here are derived from chain data — proposers from block headers, tokens from Transfer logs, contracts from creation traces. The groups marked curated come from Arcscan's address label registry, where every entry carries the evidence it was identified from: a factory relationship, a name in the contract's own bytecode, or a block header. Nothing is published on a guess, and where the evidence supports only a shape the label says the shape.
Arcscan's curated label registry holds 51 addresses, every one of them measured on Arc chain 5042002, and none of those is published here. A curated name is a claim about the code at an address, and the same address holds different code on a different chain — so a name measured elsewhere is not evidence about this one. The 6 entries the Arc execution layer itself defines — the precompile family and the two USDC faces — are published, because those are fixed by the chain rather than deployed on it, and the evidence beside each was re-read on this chain. Every other group above is derived from this chain's own data.
An address is a 20-byte identifier that can hold a balance and, when it carries code, execute it. Gas on Arc is paid in USDC, so the balance shown for an address is denominated in dollars rather than in a volatile asset.