What Is a Contract Address in Crypto and How Do You Check One?

1. What is a contract address?

Every account on Ethereum, and on the chains built like it, has an address. Two kinds of account exist. An externally owned account belongs to whoever holds its private key. A contract account holds a program and the data that program keeps, and its address is the contract address. The ethereum.org documentation states it directly: contract accounts do not have private keys; they are controlled by the logic of the smart contract code.

A contract is deployed once by a transaction, receives its address at that moment and keeps it for as long as the chain exists. Anyone can send a transaction to that address to call one of the contract's functions. A token transfer or a swap on a decentralised exchange is a transaction addressed to a contract.

Tokens are the most common case. USDT, USDC, WETH and every other ERC-20 token is a contract that keeps a table of balances. The token's address is therefore a contract address, and it is the one piece of information a wallet needs to display a token it does not know yet.

2. What does "CA" mean in crypto?

CA stands for contract address. On X, Telegram and Discord, a post about a new token usually ends with CA followed by the address, because a token's name and ticker are not unique and the address is. Trading sites and wallets use the same abbreviation.

On Solana the CA is the token's mint address, the account that defines the token's supply and decimals. On Ethereum, BNB Chain, Base and other EVM networks it is the address of the ERC-20 or BEP-20 contract. In both cases the address is what you paste into a wallet or an explorer to reach the exact token someone is talking about. That is also why fake CAs are a common scam: a lookalike token with the same name gets a different address.

3. What does a contract address look like?

The format follows the chain, and it is the same format the chain uses for wallet addresses. These are the official addresses of two widely used stablecoins, taken from the issuers' pages:

The Ethereum, Base, Arbitrum and Polygon entries come from Circle's list of USDC contract addresses, the USDT entries from Tether's supported protocols page. USDC has a different address on each chain: the same name does not mean the same contract. Upper and lower case letters in an EVM address form a checksum defined in EIP-55; the all-lowercase form is the same address, and explorers and wallets accept both.

Bitcoin has no contract addresses. A Bitcoin address that starts with 3 or bc1 can encode a script, but there is no program living at the address that you call. The concept belongs to account-based chains such as Ethereum, Tron and Solana.

4. Contract address vs wallet address: what is the difference?

On an EVM chain the two look identical, so the distinction is about what controls the address.

The one grey area is EIP-7702, live on Ethereum since the Pectra upgrade of May 2025. It lets a wallet address attach delegated code to itself so it can batch calls or let someone else pay its fees. The key still controls the account and the account can still send transactions, so it remains a wallet address with code attached.

To tell them apart, open the address on a block explorer: a contract gets a Contract tab, a creator address and, if the source was published, verified code. In code, the JSON-RPC method eth_getCode returns the bytecode stored at an address, and just 0x for a wallet address. The Etherscan guide shows where each of these tabs is.

5. How is a contract address generated?

The address is computed, not chosen, and each chain has its own rule:

Ethereum and EVM chains (CREATE)

The address is the last 20 bytes of the Keccak-256 hash of the deployer's address and its nonce, the count of transactions that address has sent. Deploying twice from the same account gives two different addresses because the nonce has moved on.

Ethereum and EVM chains (CREATE2)

A contract can deploy another contract at an address computed from its own address, a salt it chooses and the hash of the creation code: keccak256(0xff ++ address ++ salt ++ keccak256(init_code))[12:]. The address is known before anything is deployed, which is how one contract can appear at the same address on many chains.

Tron

A Tron address is 21 bytes with a leading 0x41, shown as 34 base58check characters starting with T. Contract addresses use the same format as wallet addresses and are derived from the deployment transaction's ID and the deployer's address.

Solana

A program's address is the public key of the account that stores its executable code. A token is identified by the address of its mint account, which the Token Program owns. The wallet that holds the token gets a separate token account for each mint.

The rules are in the ethereum.org accounts documentation, in EIP-1014 for CREATE2, in the Tron account reference and in the Solana token documentation.

6. Is a token address the same as a contract address?

On EVM chains, yes. A token address is the contract address of the token's contract, and wallets, explorers and exchanges use the two names for the same string. Adding a custom token to a wallet means pasting that address; the wallet then reads the symbol and the number of decimals from the contract itself, which is why a wrong address shows a wrong token rather than an error.

Two cases need an extra identifier. An NFT is identified by the collection's contract address plus a token ID, since one contract holds the whole collection. On Solana the token address is the mint address, and the balance you own lives in a token account tied to your wallet rather than at the mint.

7. How do I find a token's contract address?

Take it from a source the issuer controls, then confirm it on an explorer.

The issuer's website or documentation

Stablecoin issuers, protocols and most projects publish their addresses per chain. Circle and Tether keep one page each for USDC and USDT, and the entries in the table above come from there.

CoinMarketCap and CoinGecko

The token page lists the contract address for each chain under Contracts, with a copy button and a link to the explorer.

A block explorer

Search the token name on Etherscan, BscScan, Polygonscan, Tronscan or Solscan. Explorers mark the established token and show the number of holders; a copy with the same name and ten holders is a different token.

Your wallet or exchange

Wallets show the address in the token's details screen. Exchanges show it on the deposit and withdrawal pages, together with the network the address belongs to.

Copy the whole string and keep the network with it. A USDC address from Base means nothing on Arbitrum, and an explorer shows an empty address if you look it up on the wrong chain.

8. How do I verify that a contract address is legitimate?

The name and symbol of a token are free text in the contract, so anyone can deploy a second USDC. These checks separate the real contract from the copies:

Match it against the issuer

The address must be identical, character for character, to the one on the issuer's site or documentation. Compare more than the first and last few characters; lookalike addresses are generated to share exactly those.

Look for verified source code

On Etherscan and similar explorers the Contract tab shows whether the deployer published the source and the explorer recompiled it to match the bytecode. Unverified bytecode is a warning sign for any widely used token.

Check holders, age and activity

A real stablecoin contract has millions of transfers and years of history. A contract deployed last week with a handful of holders and no verified source is a different token, whatever its name.

Read the token's rules

Explorers and token scanners flag contracts whose owner can mint freely, pause transfers, change fees or block selling. A proxy contract keeps its address but can swap its implementation, so check who controls the upgrade.

Cross-check the chain

The same project has different addresses on different chains, so make sure the explorer, the wallet and the source all refer to the same network.

The Etherscan guide walks through the Contract tab and the Read Contract and Write Contract views used for these checks.

9. Can I send crypto to a contract address?

You can, and the result depends on the contract. Depositing into a lending pool, buying on a decentralised exchange or minting an NFT all work by sending a transaction to a contract, usually with a function call attached, through a wallet or a dApp that knows the contract's interface.

Sending tokens to the token's own contract address is the mistake to avoid. The ERC-20 standard defines transfer, approve and balance functions and nothing that lets the contract hand tokens back, so coins sent to a token contract by mistake are normally gone unless the issuer built a recovery function and agrees to use it. The same applies to most contracts that were never designed to receive plain transfers: some reject them, others accept them silently.

When an exchange or a person asks for a deposit, they give you a wallet address. When a protocol wants you to interact, the dApp builds the transaction for you. If you find yourself pasting a token's contract address into the recipient field of a transfer, stop and check what you are doing.

10. Is a contract address the same on every blockchain?

No, unless the deployer made it so. The USDC table above shows four different addresses on four EVM chains for the same asset, because each deployment was a separate transaction from an account with a different nonce. Bridged versions of a token, often labelled with a suffix such as .e, have their own addresses, so an explorer can show more than one token called USDC on one network.

Identical addresses across chains are possible through CREATE2, or by replaying the same signed deployment transaction from a fresh account on every chain. Multicall3, a helper contract used by wallets and libraries, sits at 0xcA11bde05977b3631167028862bE2a173976CA11 on more than a hundred chains for that reason, as its deployment list shows. Most tokens are not deployed this way, so look up the address on the chain you are using.

If you are unsure which network a wallet is connected to, the chain ID list maps each chain ID to its network and explorer.

11. Checking an address in code

An application that lets users paste a token or recipient address should validate the format before it builds a transaction. ChainGate's SDK validates addresses for Bitcoin, Ethereum, Litecoin, Dogecoin, Bitcoin Cash and any EVM network you register, and it rejects an EVM address whose mixed-case checksum does not match:

import { ChainGate, isValidEvmAddress } from 'chaingate';

const cg = new ChainGate({ apiKey: process.env.CHAINGATE_API_KEY });

// Format checks: true for a well-formed address, false otherwise
cg.networks.ethereum.isValidAddress('0xdAC17F958D2ee523a2206206994597C13D831ec7'); // true  (USDT contract)
cg.networks.ethereum.isValidAddress('0xD8DA6bf26964af9d7eed9e03e53415d37aa96045'); // false (EIP-55 checksum does not match)
isValidEvmAddress('0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48');                  // true  (USDC contract)

// Bitcoin: validate and classify the address type
cg.networks.bitcoin.isValidAddress('bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4');      // true
cg.networks.bitcoin.identifyAddressType('bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4'); // 'segwit-p2wpkh'

Format validation says the string is a well-formed address; it does not say whether code lives there. For that, call eth_getCode on an RPC endpoint: a contract returns its bytecode and a wallet address returns 0x. The address validation documentation lists every supported network and the Bitcoin address types the SDK recognises.

12. Where to go from here

A contract address tells you which program you are talking to, the transaction hash tells you which call you made, and the Etherscan guide shows how to read both on an explorer. Every call to a contract costs gas, and the gas tracker shows what that costs right now on each network. If you want address validation, balances and transfers handled across Bitcoin, Ethereum and the other networks from one SDK, ChainGate does that.

Frequently asked questions