Checking a swap contract address before you approve the transaction

Every swap on this site follows the same sequence. You send one cryptocurrency to an address the exchanger provides. The exchanger's system detects the arrival, converts the funds at a rate shown before you started, and sends the result to a wallet you specify. The whole operation is supposed to run without human intervention. When it works, the process takes minutes. When it does not, the gap between what you see on the blockchain and what you see on this page can be wide, and the remedies are limited.

The first and most important check is the contract address itself. Before you approve any transaction in your wallet, stop and read the address the exchanger gave you. It should be a fresh address generated for your swap, not a reused one. The exchanger does not recycle deposit addresses - each swap gets its own. If you see an address you recognise from a previous trade, or if the address looks truncated or unusual in your wallet prompt, do not approve. Cancel the transaction and reload the swap form.

Understanding exactly how to read a swap contract on a block explorer before approving is the skill that prevents most losses. Copy the contract address into a block explorer for the relevant network - Etherscan for Ethereum, Solscan for Solana, BscScan for BSC. Look for verified source code. A legitimate swap contract will show a green checkmark indicating the code matches the compiled bytecode. Check the transaction history of the contract. If the contract is hours old and has processed thousands of transactions, that pattern is normal for a hot contract. If it is hours old and has zero transactions, something is wrong. If the contract holds a large balance of the token you are sending and no mechanism to move it out, that is a red flag. The contract should have withdrawal functions and a logic path that sends funds onward after conversion.

Before you move any meaningful amount, you should learn how to test a swap address with a tiny amount first. This is not paranoia. It is the cheapest insurance available. Send the minimum possible transaction - a few cents worth, or whatever the network allows. Wait for the test to complete. If the test swap arrives in your destination wallet and the site shows the expected result, proceed with the larger amount. If the test fails to arrive, or if the site shows nothing after the test succeeded on the blockchain, you have caught the problem with negligible cost. Many users skip this step because they are in a hurry. The test takes three minutes and can save you from sending an entire balance into a dead contract.

During the swap itself, your transaction first appears on the blockchain as pending. This is normal. The exchanger's system watches the mempool and the chain for your deposit. Once the transaction has enough confirmations, the system triggers the outbound transfer. The time between your deposit confirmation and the outbound transaction depends on network congestion and the exchanger's internal queue. A stuck swap raises an immediate question: how to tell if a stuck swap is a blockchain delay or an exchange problem. Look at the block explorer for your deposit transaction. If it is confirmed - meaning it has the required number of confirmations for that network - then the blockchain is done. The delay is on the exchanger side. If the transaction is still unconfirmed after an hour, the network is congested or your gas fee was too low. In that case, the exchanger cannot act until the blockchain finalises your deposit. There is nothing the exchanger can do about an unconfirmed transaction.

When the blockchain shows your deposit as confirmed but the site shows nothing, the situation is different. What to do when a swap succeeds on the blockchain but the site shows nothing is a common support request. First, check that you sent to the correct address. If the address matches, the issue is likely that the exchanger's monitoring system has not picked up the transaction. This can happen during maintenance, or if the block explorer API the site uses is delayed. Wait fifteen minutes. If nothing changes, contact support with the transaction ID and the deposit address. Do not send a second transaction while the first is unaccounted for - you double your exposure.

When you do contact support, what details to include in a swap complaint to get a faster resolution matters more than the tone of the message. Provide the exact transaction hash from the block explorer. Include the destination address you entered. State the amount and the token type. Mention the time you sent the transaction. If you have a support ticket number from an earlier contact, include that too. Support can investigate a specific transaction hash faster than they can search for a username or an email address. Without the hash, they have to guess which transaction is yours.

Before you hit send on any swap, think about crypto-swap/">what to screenshot before you hit send on a crypto swap. Capture the page showing the deposit address and the rate. Capture your wallet's transaction confirmation screen showing the contract address and the amount. Capture the block explorer page after the transaction is sent, showing the transaction hash and the status. If something goes wrong, these three screenshots give support everything they need to verify your claim. Without them, you are asking a stranger to trust your word about a transaction they cannot see.

Occasionally, a swap site asks for more than a transaction hash. Why a swap site asks for a selfie with your ID after you already sent funds is a question that should make you stop. The only legitimate reason is compliance with anti-money-laundering regulations that apply to certain jurisdictions or amounts. If the request appears after you sent funds but was not disclosed before you started, the situation is suspicious. Legitimate compliance checks are disclosed upfront, with clear thresholds. A request that appears only after you have money in the exchanger's hands may indicate an attempt to extract personal information under duress. Do not send identity documents to a site that did not warn you. Contact support and ask for the policy in writing. If they cannot produce one, consider the funds at risk.

The hardest question to answer is how to reach a real person when swap support only sends auto-replies. Automated support systems are common. They reply with template answers that match keywords in your message. If the auto-reply does not resolve the issue, reply to it with specific data - the transaction hash, the block number, the exact error message. Auto-reply systems often escalate a thread after a certain number of human-sounding responses. Do not use angry language; automated filters flag hostility and may route your ticket to a lower priority queue. Keep the message factual and repeat the key data in every reply. Eventually, a human may review the thread.

Some problems cannot be fixed. If you approved a malicious contract that drained your wallet, the funds are gone. If you sent to the wrong network, the exchanger may never receive them. If the exchanger itself is fraudulent, no support ticket will recover your money. The checks you do before approving are the only layer of protection that matters. After the transaction is on the chain, the power to reverse it does not exist.