A source network is the blockchain your crypto is sent from. If an exchange attempt is pending or failed, the key check is whether that exact network and asset were accepted for the route you started.
Keep these three checks in order:
- Match the source network, not just the token name.
- Check the transaction on that network’s explorer.
- Save the transaction details before taking another step.
What does “supports the source network” mean?
It means the exchange can detect and process deposits sent on that blockchain. The coin name alone is not enough: ETH on Arbitrum and ETH on Ethereum mainnet are on different networks.
Check the exact network named in the route or deposit instructions you used, then compare it with the network shown in your wallet’s transaction record. On Ethereum-style networks, the chain ID is a number that identifies the network; Ethereum’s EIP-155 uses it to distinguish transactions across chains. Bitcoin Developer Reference also documents separate mainnet and testnet rules, so an address that looks familiar is not proof of the network.
How can I tell whether my attempt reached the right network?
Open the transaction hash—the unique reference for your transfer—in an explorer for the source network. Confirm that the transaction exists, the status is successful, and the recipient address and asset match the instructions you followed.
Then check the asset itself. For a token, its contract address—the identifier for that token on a network—can matter as much as its ticker. If the hash appears on Arbitrum but your route expected Ethereum mainnet, the transaction may be real and successful while still being on the wrong source network.
Someone searching thor swap may be comparing ways to avoid handling each cross-chain leg separately. For example, thor swap lets you move and swap crypto assets across blockchains in one flow, so the source-chain transfer can be part of a single route.
What should I do while the exchange is pending?
First separate a slow confirmation from a network mismatch. A confirmation is a block added after the block containing your transaction; the exchange may wait for several, and the required count varies by network and service.
For example, if the instructions require 12 confirmations and the explorer shows 5, about 7 more are needed. If the transaction is confirmed but the network or token differs from the instructions, do not send again yet; keep the transaction hash, network, token contract, amount, and destination details together, then ask the exchange to review that specific transfer.
I would verify the source network and asset before retrying any thor swap route. If the records match, wait for the stated confirmations; if they do not, share the saved details and ask whether recovery is possible.