Search

One box, at the top of every page. It takes a block height, a hash, an address, a hex fragment or a token symbol, and sends you to the page that answers for it.

What you can type#

Shapes with exactly one possible answer skip the results page entirely — you land on the block, the transaction or the address. Everything else goes to a ranked results page. Case is never a reason to fail: a mistyped EIP-55 checksum is normalised and searched, not rejected.

What you type	Example	Where it takes you
A block height	14852184	The block at that height. The box navigates straight there, so a height the chain has not produced yet lands on a block page that answers 404 — it never invents a block.
A height with its separators	14,852,184	The same block. The box strips commas, spaces, apostrophes and underscores first, because the grouped form is what this site prints in every table and tile.
`0x` + 64 hex — a transaction hash	0x128cb07d…e98251e9	The transaction. The index is consulted as well as the node, so a hash the node has already pruned from its own lookup table still resolves.
`0x` + 64 hex — a block hash	0xec5b22ac…f1221075	The block, addressed by its height — the destination is `/block/14852184`, not the hash. If one string is somehow both a transaction and a block, both are offered.
`0x` + 40 hex — an address	0xf40dc55b…6b9ae033	The address page. When there is a token interface at that address you are offered the token page and the address page and you choose; neither is picked for you.
`0x` + 6 to 39 hex — a fragment	0x128cb07d	Transactions and addresses whose identifier begins with it. Fewer than six hex characters is not searched at all, and block hashes are not searched by fragment.
A token symbol or name, 2–32 characters	USDC	Token contracts whose own `symbol()` or `name()` matches — at most five of them — alongside anything the curated label registry knows by that name.
A label, protocol or category word	arc	Addresses the curated label registry names. The match may be on the label itself, on its protocol, or on its category.

Why six hex characters is the floor for a fragment

A fragment shorter than that is a category rather than a search: one hex character selects a sixteenth of the chain. The list would be cut by a limit and handed to you ordered by hash, which looks exactly like a ranking and is not one. At six characters the answer almost always fits, so what comes back is the whole answer rather than a slice of it.

The dropdown, and what it does not prove#

The list under the box appears about 140 ms after you stop typing. It is capped — the API is asked for eight rows and the merged list never exceeds ten — and it is not paged: it is the best few answers, not all of them. It offers destinations for complete identifiers without asking the chain first, which is a deliberate trade against one RPC call per keystroke — so 0x followed by 64 arbitrary hex characters is offered as “Transaction” even when no such transaction has ever existed. Press Enter instead and the results page does ask, and answers “Could not find any matches!”. Treat the dropdown as a shortcut, not as evidence.

There is no fuzzy matching anywhere in this box

Every predicate behind it is an exact value or a leading-fragment range. Nothing is stemmed, corrected or expanded, there are no “did you mean” suggestions, and % is an ordinary character rather than a wildcard — it matches no name and returns nothing.

When several things match#

The results page groups what it found under Addresses, Tokens, Blocks and Transactions, in that order. Within a group, knowing the identifier exactly outranks matching a fragment of one, which outranks matching a name; and an address the label registry names outranks one it does not. That single ranking is shared by the dropdown and the page, so the first row is the same in both.

You can narrow the search to one group. The wide field — the home-page hero and the search page itself — carries a scope selector to the left of the input; the compact field in the site header does not. Either way the scope lives in the URL, so a filtered result is a link you can send:

https://arc-scan.io/en/search?q=usdc&f=token

f = all | address | token | block | tx     (default: all)

Below 576 px even the wide field hides its selector, to keep the input usable on a phone; the f parameter still works there. See the search pageOpens in a new tab for the live form.

A symbol is a claim, not an identity

Any contract can call itself anything. Several on Arc mainnet answer to USDC, so a symbol search caps the token rows at five, sorts the address the registry actually names first, and marks every other row whose symbol is one reserved for the chain’s own assets. That mark is a fact about the name — an honest wrapper earns it too — and never an accusation. Only the address identifies a token; compare it against Tokens before you act on a match.

When nothing matches#

You get “Could not find any matches!” and a note on what the accepted shapes are. Nothing is guessed and no near-miss is substituted. The usual causes, in order of how often they are the real one: a character lost in a copy; a fragment shorter than six hex characters; a word that is neither a token symbol nor a curated label — Arc has no name service, so there is nothing else for a word to resolve against; or a scope filter still set from an earlier query, in which case widening it back to all is the whole fix.

Resolving is also not the same as our holding indexed data for the destination. The box can send you to a block or an address whose derived detail is outside what has been indexed, and that page will say so in prose rather than print a zero. Data coverage states exactly which ranges are held on each chain.

A hash from the other chain#

Mainnet and testnet are two deployments over two separate indexes, reached by two hostnames. A mainnet hash pasted into testnet’s search box returns no match, and the reverse is equally true — measured, not assumed. Neither host forwards a query to the other and neither guesses that you meant the other chain, so if a hash you trust returns nothing, check which hostname you are on before anything else.

Which host holds which chain

arc-scan.io is Arc mainnet, chain 5042. testnet.arc-scan.io is Arc Testnet, chain 5042002. A hash is only meaningful on the chain that produced it.

Keyboard, and the limit on a query#

Key	What it does
`/`	Focuses the search field from anywhere on the page, unless you are already typing in a field.
`Enter`	Opens the highlighted suggestion if there is one; otherwise submits the query. On an empty box it says what the field wants instead of doing nothing silently.
`↑ ↓`	Moves through the suggestion list. The selection wraps at both ends and focus stays in the input.
`Escape`	Closes the suggestion list and leaves what you typed alone.

The field stops at 68 characters, which is longer than the longest legitimate query — a 66-character hash. The API behind it refuses anything past 128 characters outright rather than quietly trimming it, so you cannot reach that ceiling through the box at all and nothing you type is ever silently shortened. Nothing about what you type is stored: the search analytics classify the query by shape and then discard it, and a string shaped like a secret — a seed phrase, a bare private key — is dropped without recording that it was seen at all.

Where each destination takes you next is covered by Blocks, Transactions, Addresses and Tokens. If something here still does not match what you are seeing, FAQ collects the cases that come up most.