Search an EVM network's name or exact chain ID in the lookup, then compare two results as network A and network B. Decimal and hexadecimal can describe the same ID: Base's 8453 is 0x2105. Matching currency symbols or address formats do not make different networks interchangeable.
Find a chain ID step by step
- Open the lookup and enter a network name, native-currency symbol, decimal ID or
0x-prefixed hexadecimal ID in Name, currency or chain ID. Names and symbols may match several records. - For a specific ID, inspect the exact match and its decimal/hex representations. The tool uses exact integer conversion, including IDs too large for ordinary JavaScript integer precision.
- Read the name, native currency, registry status and any warning. Expand secondary registry details when needed.
- Compare the result against your wallet's network details and the receiving service's current deposit instructions. The lookup supplies dated community metadata, not live configuration approval.
Compare Ethereum and Base
- Choose the Ethereum example and select its result as network A.
- Choose the Base example and select its result as network B. The selected comparison remains available while you search.
- Read the outcome, then expand the registry fields for each selected network.
- Select Download comparison notes (.txt) to retain the snapshot date, IDs and warnings. Use Clear search & comparison to remove both selections.
| Network | Decimal chain ID | Hex chain ID | Listed native symbol |
|---|---|---|---|
| Ethereum Mainnet | 1 | 0x1 | ETH |
| Base | 8453 | 0x2105 | ETH |
Both entries list ETH, but their IDs differ. The useful outcome is identifying that difference before reviewing the intended route. The tool does not move ETH between networks or establish that a deposit service supports either route. A shared symbol also does not identify a token contract.
Read decimal and hexadecimal correctly
Hexadecimal uses base 16 and commonly begins with 0x. The lookup accepts 0X00002105 and displays its canonical equivalent 8453 = 0x2105. Search an ID rather than relying on an ambiguous shortened name. If an exact conversion is valid but no entry matches, the bundled snapshot does not contain that ID; it does not prove the ID is unused.
Do not confuse chainId with a separate networkId field. Check what your wallet or application is asking for. This lookup reports the registry's chain ID.
Use status and warning filters correctly
Registry status lets you narrow records, including deprecated or incubating entries. Only entries with test/development indicators filters detected metadata indicators. These labels are not a live availability check, exhaustive testnet classification or security assessment. An entry without a warning is not necessarily suitable for your intended transfer.
The displayed snapshot date identifies the included data. Downloaded notes retain that date so another reader can tell which snapshot you compared. Confirm current network support directly with the service handling your deposit before using the information.
Troubleshoot mismatched results
- A search returns several networks
- Use an exact numeric ID from the wallet's details, then verify the full network name and receiving instructions.
- Both results use ETH, but the wallet shows different balances
- Read the different chain IDs. The lookup does not aggregate balances or bridge funds.
- A 0x address looks valid on both networks
- The address format alone does not determine the intended network or recipient support. Obtain the network from the receiver's instructions.
- I cannot download comparison notes
- Select both network A and network B first. A single search result is not a completed comparison.
Questions about network lookup
Does the tool add a network to my wallet?
No. It omits RPC configuration and does not connect wallets. Read your wallet's official instructions for any configuration task.
Does “active” guarantee an operational network?
No. It is registry metadata, sometimes a default when no explicit status is supplied. It does not verify current block production or RPC health.
Can a chain ID confirm the exact USDT or USDC asset?
No. You also need the recipient's supported asset variant and network, and the appropriate token-contract identity where relevant. Continue with the transfer checklist and USDT/USDC guide.
Sources and next steps
Examples use the pinned ethereum-lists/chains snapshot shipped with the tool. The guide describes the tested local interface; it makes no live RPC or wallet-state claim. Compare the amounts a hypothetical route could deliver after separately confirming supported networks and assets.