How to Use Arcscan, Arc’s Block Explorer

Arcscan is where claims about Arc get checked. A wallet shows you an interface; a project shows you a marketing page; the explorer shows you the ledger. Learning to read it is the difference between believing a lock exists and knowing one does.

Works on Arc testnet today; mainnet September 16, 2026.

Where is Arcscan?

The public testnet explorer is at testnet.arcscan.app. The mainnet explorer host has not been published — public mainnet opens September 16, 2026, and Circle will publish the mainnet chain ID, RPC and explorer at arc.io and docs.arc.network then. Do not trust a third-party site that claims to already be the Arc mainnet explorer.

Reading a transaction

Paste a transaction hash into the search bar and you get the canonical record. The fields that matter:

• Status. Success or failure. A failed transaction still costs gas and still appears on chain; plenty of "it went through" claims dissolve here.
• From and To. The sending address and the receiving address or contract. On a token transfer, the To is the token contract, and the actual recipient shows in the transfer log below.
• Value and token transfers. Native value moved, plus a decoded list of any ERC-20 transfers the transaction produced.
• Transaction fee. Denominated in USDC, because that is Arc's gas token. Testnet averages have run around $0.004. Why the fee is a stablecoin.
• Block and timestamp. Arc finalises deterministically in roughly 780ms, so the block containing your transaction is settled, not pending confirmation depth.

Reading an address

Search an address and you get its balance, transaction history, and — for contracts — the code tab.

For a wallet, the useful signals are age, funding source and counterparties. A "team wallet" created three days before a launch tells you something.

For a token contract, go straight to the holders tab. What you are looking for is concentration: how much supply sits in the top wallet, and whether the top holders are locks and pools or anonymous addresses. A token where one non-lock wallet holds 40% of supply is a token with a single exit button.

Verifying a contract

A verified contract publishes its Solidity source alongside the deployed bytecode, and the explorer confirms they match. Unverified means you are trusting a description of the code rather than the code.

On the contract tab, verified source appears with a Read Contract and Write Contract interface. Read functions let you query state directly — owner, total supply, balances, pause flags — without any intermediary. That is the most useful safety tool the explorer offers, because it answers questions the project's own website cannot be trusted to answer.

Things worth reading on any new token: is there an owner, and can the owner mint? Is there a pause or blacklist function? Are transfer fees adjustable, and what is the cap?

Confirming a liquidity lock

This is the check most people get wrong. A screenshot of a lock is not a lock. The chain-level version:

1. Find the LP token contract for the trading pair.
2. Open its holders tab.
3. Confirm the LP tokens are held by a locker contract, not by a deployer wallet.
4. Open the locker contract and read the unlock timestamp for that position.
5. Check the amount: a lock covering 5% of the pool is not a locked pool.

The full step-by-step, with the traps, is here.

Using the explorer during a launch

If you are the one launching, the explorer is also your proof surface. After you mint, lock and vest, the links you publish should be explorer links — the token contract, the lock position, the vesting schedule. Buyers who know how to check will check, and buyers who do not will still recognise that you gave them something checkable.

Team Finance produces exactly those artefacts: locks and vesting schedules that live in audited, non-custodial contracts you can point at on chain. It has secured more than $2.7 billion across 40,000+ projects on 26 chains since 2020. Start with minting a token on Arc, then lock the liquidity and vest the team allocation.

Practical habits

• Reach the explorer by typing the address, not by clicking a link in a message.
• Cross-check any number a project gives you — supply, holders, lock duration — against the chain before acting on it.
• On testnet, remember that everything you see is test data with no value, including tokens designed to look valuable.