Find the network at the source
The network field in the sending wallet or exchange record is stronger evidence than the shape of an address.
Paste one public wallet address or transaction ID. The tool compares its visible format with common blockchain patterns and explains what can—and cannot—be inferred.
Use an address or TxID copied from a public wallet view or transfer record.
Do not enter a seed phrase, private key, password, verification code or API key. This tool is only for public addresses and public transaction IDs.
✓ The entered value is processed in this tab and is not transmitted by the checker.
The result will appear here. The checker does not send or store the value you enter.
The network field in the sending wallet or exchange record is stronger evidence than the shape of an address.
An address shows an account or script destination. A transaction ID points to one public transaction. An exchange order number is usually neither.
For deposits and withdrawals, the complete network name on both sides must match. A familiar prefix is not enough.
Every row says “candidate” because format matching is not full validation.
| Possible family | Visible pattern | Important limit |
|---|---|---|
| TRON / TRC-20 candidate | T + 33 Base58 characters | A format clue only; checksum and account are not verified. |
| EVM address candidate | 0x + 40 hexadecimal characters | Shared by Ethereum, Base, Arbitrum, OP, BSC, Polygon, Linea, Avalanche and more. |
| Bitcoin address candidate | Commonly starts with 1, 3 or bc1 | Network and checksum still need confirmation. |
| Solana candidate | Base58, commonly 32–44 characters for an address | Base58 patterns can overlap with other systems. |
| TON candidate | EQ / UQ user-friendly form, or 0: / -1: raw form | Bounceable status and checksum are not fully validated here. |
| Cosmos ecosystem candidate | Bech32 prefix + 1 + data | The visible prefix is a clue, not proof of account type or ownership. |
A 42-character 0x string is a common EVM address shape, not a network label. Ethereum, Base, Arbitrum, OP Mainnet, BNB Smart Chain, Polygon, Linea and Avalanche C-Chain can display the same account address.
Safe conclusion: you may have an EVM-format address, but you still need the sending record or receiving deposit page to identify the chain.
A 66-character 0x hash and a 64-character hexadecimal hash are used by multiple chains. A Solana signature uses a different Base58 pattern, but even that visible clue is not proof.
Best evidence: open the original withdrawal or transfer record and read the asset, full network name, destination and TxID together.
A 42-character 0x address is an EVM-format address. The same format is used by Ethereum, Base, Arbitrum, OP Mainnet, BNB Smart Chain, Polygon, Linea, Avalanche C-Chain and other EVM networks. The address alone cannot identify the chain.
No. It checks visible formatting only. It does not verify a checksum, account existence, ownership, balance, token support or whether an exchange accepts deposits to that address.
Start with the withdrawal or transfer record on the sending platform and read its network field. Hash formats overlap across chains, so the TxID text alone may not identify the network.
No. Several chains and systems use 64-character hexadecimal transaction hashes. It can also resemble secret-key material, so only paste a value explicitly labelled as a public TxID or transaction hash.
A public wallet address or public transaction ID can be checked, but it may still reveal public on-chain activity. Never paste a seed phrase, private key, password, verification code or API key.
Base58, Bech32 and other encodings can overlap, and this tool does not query a blockchain or validate every checksum. A format clue is useful for narrowing the search, not proving the network.
No. The checker processes the entered value in this browser tab and does not submit it to this site or to a block explorer. Confirm the actual network in the sending platform before using an explorer.
Reviewed September 12, 2026. The checker processes the entered value locally and does not query a blockchain.