[ Thread 01 · read-only ]

“I sent to the right address, but maybe the wrong network”

by chain_reader 2026-04-22 14 replies 1820 views
Network mismatch Beginner Transaction hash
Original post

I sent a transfer earlier today and the receiving address looks identical to the one I expected. Funds left my wallet, the transaction shows as confirmed in my history, but the receiver says they see nothing. I am starting to suspect the network selection, not the address.

I’ve seen people warn about this for years and I never thought it would happen to me. The interface showed the asset by its short name, I tapped send, the address pasted cleanly, the confirmation screen looked normal. The detail I now realise I never double-checked is the network name above the amount.

Before anyone offers help: I will not share my seed phrase, my private key, my password or any backup code. I am happy to share the public address and the transaction hash on a public explorer, plus the network I think I used.

Section 1

What usually causes this

  • A token name like “USDT” or “ETH” can exist on several chains. The wallet UI groups them together visually, but on-chain they are completely different assets.
  • A receiving address generated for one EVM chain will look valid on every other EVM chain, because the format is the same. Looking valid is not the same as being the right destination.
  • The sending wallet remembers the last network you used. If you switched networks earlier in the day for a different reason, you can carry that selection into a transfer that should have used a different one.
Section 2

How to investigate without panicking

  • Open a public block explorer for the network you actually used. Paste the transaction hash. Read the status, block confirmations, sender, receiver, asset and amount.
  • Cross-check the receiver address on the explorer of the network they expected. If the address shows zero history there, that is strong evidence of a network mismatch, not a lost transaction.
  • Document what you have: the network name, the explorer link, the timestamp, what you intended and what happened. That is the post that gets a useful reply.
Section 3

What good replies look like

  • They ask for the network and the explorer link first.
  • They never ask for seed phrase, private key, password, recovery code or remote access.
  • They explain the difference between “funds moved on chain X” and “funds arrived on chain Y” instead of guessing.