Receiving address vs token contract address
A receiving address identifies the destination account. A token contract on EVM, or mint on Solana, identifies the asset. They serve different fields.
Worked example
| Task | Identifier needed | Example label |
|---|---|---|
| Receive tokens | Recipient’s receive/deposit address | To / Recipient |
| Import token display | Token contract or mint | Token address |
| Identify an NFT | Chain + contract + token ID | Collection contract / Token ID |
A useful separation
An ERC-20 balance is tracked by a token contract against account addresses. Looking up the contract tells you which token you are inspecting; it does not tell you where a person wants a payment sent. Solana separates mint and token accounts in its own model.
When a page says “address”
Read the surrounding field name. An explorer token tracker, a wallet Receive button and an NFT import dialog all display addresses for different purposes. Record the role alongside the string instead of copying a naked value into a new context.
Common pitfalls
- Do not send funds to the collection contract shown in this directory.
- A recognizable token name can be copied by an unrelated contract.
Related references
Primary sources
Examples explain identifiers. They are not investment recommendations.