If a swap is pending, look up its transaction hash on the Avalanche C-Chain explorer before trying again. A hash is the transaction’s unique ID; it lets you check what the network has recorded. For a swap through Blackhole swap, that record can show whether the request was included and whether it succeeded. The how to use Blackhole swap article is useful context for the exchange itself, while the explorer shows the transaction’s on-chain result.
What does “pending” mean for a swap?
“Pending” means the explorer has not yet shown a completed result for that transaction. It does not prove the swap is still progressing, or that it will succeed. The wallet signs the request, sends it to a network node, and gets a hash; the explorer then looks for the transaction in its data.
A swap asks a smart contract—a program on the blockchain—to trade one token for another. Until the transaction is included in an accepted block, the explorer cannot show its final result. On Avalanche C-Chain, accepted transactions are final, but an explorer can take time to update.
Start with the hash from your wallet’s activity record. Search it on an Avalanche C-Chain explorer. If nothing appears, check that the wallet sent the transaction on C-Chain and that you copied the full hash. A missing result can mean the explorer has not seen it; it does not by itself mean funds are lost.
What should you check once the transaction appears?
Check the transaction status first: success or failure. Then check the transaction receipt, the network’s record of execution, and its token transfer events. Events are entries the contract writes during a swap. They help show which tokens moved and how much reached your wallet.
For example, say you swap AVAX for a token and the transaction succeeds. The transaction details may show a contract call, while transfer events show AVAX or WAVAX—the token form of AVAX—going in and the other token coming out. The output amount and your token balance are better evidence of the result than a “pending” label or the wallet’s initial estimate.
A failed swap can still cost gas, the network fee for running the transaction. On C-Chain, that fee is paid in AVAX. A failed receipt means the swap’s changes were undone; it does not mean the fee was refunded. A contract can reject a swap if its price limit, often called slippage tolerance, is exceeded before execution.
What if it stays pending?
Check the sender’s other transactions and their nonce, a number that orders transactions from one wallet. If an earlier transaction is stuck, later ones may wait behind it. A replacement transaction with the same nonce can supersede the original, so searching both hashes may show one pending and one completed—or only the replacement.
Do not send the swap again just because the explorer looks slow: two attempts can both execute. Check the wallet’s status and the hash first. If Blackhole swap is where you started, use its transaction hash to follow the C-Chain record; the explorer reports what happened on-chain, not what the exchange screen currently displays.
Does pending mean the swap failed?
No. It means you do not yet have a completed result in that explorer. Confirm the hash and C-Chain selection, then check again. If a receipt appears, its success or failure status settles the question. If the hash remains absent, the explorer may not have received it, or the transaction may have been replaced.
Can I close my wallet while it is pending?
Yes. Once a signed transaction has been sent, closing the wallet does not cancel it; the network handles the request. Save the hash first so you can look it up later. Reopening the wallet or reconnecting it does not change the transaction’s on-chain status.
Which detail best proves a swap worked?
Look for a successful receipt and the token transfer events, then confirm the received amount in your wallet on C-Chain. A wallet notification alone can be stale, and a successful transaction can call a contract without producing the token output you expected. The receipt and events show what the contract actually did.
Takeaway: Follow the hash, then trust the receipt and transfer events over a pending label.