A pending cross-chain swap is not automatically stuck. Your first transaction may be confirmed while the transfer to the other network is still underway.
- Check the source transaction before taking action.
- Look for a separate destination transaction and the right asset.
- Retry only after you know what happened to the first attempt.
Why one swap can have more than one transaction
A cross-chain swap moves value between separate blockchains, which keep separate transaction records. The service coordinating the move must detect your payment on the first network, then arrange the matching delivery on the second.
Think of it like checking a bag on a connecting flight: the first leg can finish before the bag reaches its final stop. For example, the quickswap swap service lets someone move and swap assets across networks in one flow; the source payment and destination delivery still happen on their respective networks.
Depending on the route, a bridge may lock or burn the source asset, then release or create an equivalent asset on the destination. A liquidity-based route may instead pay from funds already available there. These are different mechanisms, so a pending label alone does not tell you which step is waiting.
Check the source transaction first
Find the transaction record for the asset you sent on the starting network. A transaction ID, sometimes called a hash, is the unique string used to look it up in that network’s public explorer, a site that displays confirmed network activity.
Check that the record shows the correct asset, amount, and destination details, then read its status. A Bitcoin transaction may show zero confirmations while it waits for a block; each later block adds a confirmation. Bitcoin’s public block explorers show these counts, which help explain why the wait can vary.
If the source record says failed, the network did not complete that payment. If it is still pending, wait and check again rather than sending the same amount a second time. A confirmed source payment means only that the first leg happened; it does not prove the destination delivery is finished.
Look for delivery on the destination network
Check the destination wallet on the network you selected, and search its explorer if the receiving transaction is available. A destination transaction has its own record and may have a different ID from the source transaction.
Confirm that the wallet is showing the intended network and asset. Some wallets hide tokens until you add them to the display, so a missing balance does not always mean the transfer failed. A token that represents value bridged from another network may also have a different label from the original asset.
Solana’s explorer shows transaction states such as confirmed and finalized; finalized means the network has reached its strongest confirmation state. The Solana documentation explains these states. If the destination record shows a failed transaction, or no delivery appears after the route’s stated wait, keep both transaction IDs and the amount ready when seeking help through the service you used.
Decide whether to wait or try again
Wait when the source transaction is still pending or the route appears to be processing it. Network congestion, the number of confirmations required, and the route’s own checks can all affect timing, so there is no single wait time that fits every swap.
Do not repeat the transfer just because the destination balance has not changed yet. If the first transfer later completes, a duplicate could send a second amount. If the source clearly failed, check your wallet’s available balance before starting over; the failed attempt may not have moved the funds.
When the source is confirmed but the destination remains missing beyond the expected wait, compare the source and destination records before doing anything else. Make sure you selected the right receiving network and address. Those details help distinguish a delayed route from a wallet display issue or a delivery to a different destination.
Does a confirmed source transaction mean the swap is complete?
No. It confirms that the first network recorded your payment, but the destination network may still need to record the delivery. Check for the destination transaction or the asset in the wallet on the correct network before treating the swap as finished.
Should I start another swap if the first one is slow?
Not until you know the first attempt failed or completed. Check its source record and destination status first. If the source was confirmed but delivery is missing beyond the expected wait, use the transaction details to ask the service you used what happened.
Follow both transaction records from payment to delivery, and retry only when the first attempt’s status is clear.
Top comments (0)