Wallet address vs contract address vs transaction hash
An EVM wallet address and contract address share the same 20-byte display shape. A transaction hash identifies a transaction and is normally 32 bytes.
Worked example
| Input | Shape | Where it belongs |
|---|---|---|
| EOA or contract | 0x + 40 hex characters | Explorer address field |
| Transaction hash | 0x + 64 hex characters | Explorer transaction search |
| NFT token ID | Integer within a contract | NFT import token-ID field |
Worked import mistake
Pasting a transaction hash into an NFT contract field adds 24 extra hex characters. Pasting the wallet that owns the NFT has the expected address length but the wrong role. Find the asset’s collection contract in the item details, then copy its token ID separately.
Role requires network context
A format check can separate common lengths, but it cannot prove that code exists at an address. Inspect the contract tab and token tracker on the correct explorer. Source-code verification concerns bytecode correspondence, not project authenticity.
Common pitfalls
- An address is not a transaction receipt.
- Contract and wallet cannot be reliably distinguished by 0x syntax.
Related references
Primary sources
Examples explain identifiers. They are not investment recommendations.