Guide Wallets and security Ethereum and other coins

How to check a token by its network and contract address

To identify a token on an Ethereum-compatible network, compare two details together: the exact network and the full contract address. Obtain them from an official project source and check them against the appropriate block explorer. A familiar name, ticker and picture can belong to a different token. An address match helps identify an asset; it does not certify that it is safe or worth buying.

A magnifying glass over an orange cube in two separate groups of connected cubes
Illustration: examining an identity within a particular network, without real addresses or data.

The check answers a narrow but important question: is this the token you intended to display or use? It comes before questions about price, returns or suitability. You can perform it as a read-only exercise, without connecting a wallet or signing a request.

Three details that are easy to confuse

A wallet address is the address used to receive assets. A token contract address identifies the software managing that token's balances and operations on a network. A transaction identifier refers to a particular operation. All three may appear in the same block explorer, but they serve different purposes.

MetaMask's documentation explains that a contract receives its address when deployed on the network. ERC-20 defines a shared interface for tokens, including fields such as a name and symbol. Those fields are not a registry of unique names. Ethereum's guide to impersonation tokens (Opens in a new tab) shows that different contracts can use the same symbol or similar names.

This guide concerns contract-based tokens on Ethereum-compatible networks. Do not apply the procedure automatically to every asset. Bitcoin on the Bitcoin network, for example, is not an ERC-20 token with this kind of contract address. A product representing bitcoin on another network needs separate scrutiny of its mechanism and the organisation behind it.

A repeatable checking process

  1. Identify the network. Note its name in both the project's documentation and the interface you intend to use. Similar asset names do not make two networks interchangeable.
  2. Reach the official source. Open the project website through a known route and find its address list. An address supplied in a reply, advertisement or private message is not a sufficient reference point.
  3. Open the right explorer. Choose the block explorer for that network and look up the address obtained from the official source. Reading its public page does not require approving an action in your wallet.
  4. Compare the entire address. Check that the complete text was copied without substitution or truncation. Comparing only a few characters at the beginning and end leaves part of the identity unchecked.
  5. Check the destination separately. If planning a transfer to a service, establish that it supports that token on that network. A correct contract address does not guarantee a particular service will accept a deposit.

You can retain a non-secret record: project name, network, contract address, source-page URL and the date checked. That avoids starting from a random search result every time. Do not put a private key or recovery phrase in that record.

An example: the same ticker on two networks

Suppose a project's website lists versions of a token on two networks, and a wallet displays the same ticker for both. You want the version on the first network. Start with that network, copy its official contract address and compare it with the interface. A match to the version on the second network does not resolve the check, even if both versions are legitimate.

If the receiving service supports only the second network, do not conclude that you can send through the first. Stop and check its instructions. This guide does not prescribe a bridge, swap or recovery route: each has separate conditions and risks. The purpose of the example is to spot the mismatch before money is sent.

Another example is a token that appears in your wallet without being requested. A familiar name and large balance do not prove that the original project sent it. You do not need to visit a website in the token's name or approve spending permissions merely to hide it from the interface. If its identity is unclear, avoiding interaction keeps the check at the reading stage.

What the check cannot guarantee

Identifying a contract is not a security audit. It does not inspect every administrative permission, the ability to change code, sellability or the issuer's financial position. A holder count, professional design or presence in an explorer is no substitute for that assessment. Matching the intended identity is a starting point, not a quality certificate.

Adding a token to a wallet's display also does not move it to another network or give it value. MetaMask's documentation describes manual addition using contract details to display a token. Distinguish that from a request for spending permission or sending a transaction. If an action intended only for reading requests a secret or an approval you do not understand, stop.

Alongside asset identification, understand who holds the wallet's keys. The checks complement each other: one establishes which asset it is, the other who can act on it. Neither recommends buying a token, but together they support better-informed operational decisions.

Correction and clarification

Found an error? Contact the editors

Share article Back to top