Crypto wallet and address examples
Crypto addresses identify accounts, assets or contracts in a particular network. Start with the format, then confirm the network and role before using an identifier.
NFT collection contract addresses
Choose a collection to see its contract address, network, variant notes and sources.
Choose the identifier you need
A visible address is only one part of the context. Compare encodings, check the receiving network and keep account identifiers separate from asset identifiers.
| Task | Required context | Common mistake |
|---|---|---|
| Receive a token | Asset, network, recipient address, any memo/tag | Pasting the token’s contract |
| Look up an NFT | Network, contract, token ID | Pasting its owner’s wallet |
| Check EVM spelling | Complete 0x string | Assuming a checksum identifies the network |
Guides and tools
NFT identifiersContract, wallet, token ID and metadata.NFT collection contract addressesSearch official mappings and selected variants.Bitcoin, Ethereum and Solana address formatsCompare Bitcoin, Ethereum and Solana address encodings and learn what a visible prefix can and cannot establish.Ethereum 0x address format explainedRead the prefix, byte length and hexadecimal body of an Ethereum address using a documented EIP-55 example.Bitcoin legacy, P2SH, SegWit and Taproot addressesCompare Bitcoin mainnet address families, output types and compatibility checks before choosing a receive address.Solana wallet, mint and token-account addressesDistinguish a Solana owner wallet, token mint and token account even though all use the same account-address encoding.Wallet addresses, public keys and private keysUnderstand which wallet identifiers are public and why an Ethereum address is different from its full public key.Wallet address vs contract address vs transaction hashTell account identifiers apart from transaction hashes and choose the correct field in an explorer or NFT import form.Same EVM address on different networksUnderstand when an EOA can share an address across EVM networks and why contracts and balances must be checked per chain.Ethereum capitalization and EIP-55 checksumsLearn how EIP-55 uses Keccak-256 to capitalize an Ethereum address and what a checksum can detect.Can you identify a blockchain from an address?Use address prefixes as limited clues and learn why a 0x address cannot identify its EVM network.How to find your wallet receive addressFollow a receive-screen checklist that keeps the account, asset, network and deposit instructions together.Receiving address vs token contract addressSeparate the recipient wallet from the contract or mint that identifies an asset when copying token details.USDT and USDC: choose the network before the addressDisambiguate stablecoin receive instructions by asset and network without mistaking a token contract for a deposit destination.ENS names vs Ethereum addressesUnderstand how an ENS name resolves to an address and why a name is not a permanent substitute for network-specific confirmation.What does a crypto address QR code contain?Distinguish a plain address QR code from a payment URI and verify the decoded payload before relying on it.Public addresses, explorer history and address reuseUnderstand how publishing or reusing an address can link public activity and why a public address is not anonymous.Address poisoning and look-alike recipient stringsRecognize why copying a destination from transaction history can select an attacker-controlled look-alike address.Testnet vs mainnet address identifiersLearn why Ethereum testnet addresses can look identical to mainnet and why explorer network selection matters.Crypto memos and destination tagsUnderstand why some hosted deposits need an address plus a memo or destination tag to identify the credited customer.The Ethereum zero address is not a receive exampleUnderstand the all-zero Ethereum address as a protocol sentinel and why syntactically valid does not mean usable for receiving.How to inspect an address on a blockchain explorerUse explorer address, contract and token fields to check context while keeping source-code verification separate from identity and safety.Solana program-derived addresses explainedDistinguish Solana PDAs from keypair wallet accounts and understand why not every account address has a private key.Bitcoin address case rules: Base58, Bech32 and Bech32mKnow when changing Bitcoin address capitalization breaks the encoding and why mixed-case Bech32 text is invalid.Ethereum payment URIs and chain-qualified addressesRead the target, optional chain ID and operation in an EIP-681 URI without confusing the entire request with a bare wallet address.NFT contract, wallet address and token IDIdentify the three different fields used to locate an EVM NFT and explain why the owning wallet is not the collection contract.How to find an NFT contract address and token IDLocate an NFT’s chain, contract and token ID in item details and cross-check them without connecting a wallet.NFT import errors: personal address detectedDiagnose a wallet or unsupported-contract address pasted into an NFT import field and check the required network and token ID.NFT collection vs individual token identifiersDistinguish a marketplace collection grouping from the contract and token ID that identify an individual NFT.ERC-721 vs ERC-1155 token IDsCompare unique ERC-721 ownership with ERC-1155 per-ID balances and understand why a token ID is not always a single edition.NFT token IDs: decimal, hexadecimal and large integersRead uint256 NFT token IDs without truncating large values or mistaking display formats for different tokens.ERC-1155 URI examples and the {id} placeholderWork through the 64-character lowercase hexadecimal token-ID substitution used by ERC-1155 metadata URIs.NFT metadata URI vs contract addressSeparate the on-chain NFT ledger from the URI for JSON metadata and the media link inside that JSON.How to verify an NFT collection contract identityBuild an evidence chain from an official project mapping to a network-specific explorer and distinguish identity from source-code verification.Original, wrapped and bridged NFT contractsUnderstand why an NFT’s original ledger, wrapper and bridged representation require separate network and contract identifiers.How to read NFT ownership without connecting a walletUse ERC-721 ownership and ERC-1155 balance queries to inspect public holdings while keeping claim rights and approvals separate.NFT owner, approved address and operator are different rolesRead ERC-721 approvals and ERC-1155 operator permissions without mistaking an approved account for the NFT owner.Read NFT identifiers from an item URLRecognize chain, contract and token-ID components in marketplace item links and cross-check them with visible details.EVM address format and EIP-55 checksum checkerCheck 20-byte EVM address syntax and actual Keccak-256 EIP-55 capitalization locally in your browser.
Before relying on an example
Specification fixtures are public text examples, not receiving instructions. Shapes containing an ellipsis or labels such as CONTRACT and CID are incomplete placeholders. A well-formed identifier does not establish a recipient, project identity or safe interaction.
Related references
Primary sources
Examples explain identifiers. They are not investment recommendations.