How to Check a Pending Chainflip Swap

To check a pending Chainflip swap, find its record in Chainflip Scan and identify whether it is waiting for a deposit, confirming one, executing the trade, or sending the output. Each stage belongs to a different part of the route. A source-chain transaction hash shows whether your payment was broadcast and confirmed; the swap record shows what the protocol has done with it. For a separate explanation of how the routes differ, see Chainflip's four routes for wallet swaps. Route choice is distinct from the progress stages below.

How do I find my pending swap?

Search Chainflip Scan using the source transaction hash, swap ID, or deposit address. Open the matching record and check the source and destination chains, assets, and destination address. Those details help confirm you are looking at the right transfer, especially if you have made more than one swap.

If you have the source transaction hash, open it in the source chain’s own explorer too. That view reports whether the transaction is still pending in the chain’s mempool or has been included in a block. Chainflip’s record answers a different question: whether validators have observed the deposit and where it sits in the swap process. The two records are like receipts from separate desks; each confirms a different handoff.

What does each pending status mean?

A pending label only makes sense when you know which step is unfinished. The Chainflip SDK names the stages `WAITING`, `RECEIVING`, `SWAPPING`, `SENDING`, and `SENT`; a swap can then become `COMPLETED` or `FAILED`. Interfaces may use reader-friendly labels, but the underlying sequence follows the movement of funds.

• Waiting: A deposit channel is open, but no deposit has been registered. Check that you sent funds to the address for this swap.
• Receiving: The deposit has been detected, and the source chain’s required confirmations are still relevant. Check its transaction record before concluding the swap is stuck.
• Swapping: The deposit has been witnessed and the trade is being processed against Chainflip liquidity.
• Sending or sent: The trade has executed. The output is being prepared or broadcast to the destination chain, where its transaction can be checked separately.

Confirmation time depends on the source chain, while delivery also depends on the destination chain. A quiet interval between those steps does not by itself show that the swap has failed. Look for the latest state and transaction hash, then verify that hash on the chain where it was sent.

What should I do if the swap still looks pending?

Use the stage to decide what to check next. For `WAITING`, verify the deposit address and source transaction. For `RECEIVING`, check confirmation progress on the source chain. For `SENDING` or `SENT`, look for an outbound transaction and check it on the destination chain. If the record says `FAILED`, inspect its details for the associated transfer or refund information.

Do not send a second deposit just because the first transaction has not appeared in the swap record yet. First confirm the original transaction’s status and that it went to the intended address. A pending source transaction and a confirmed deposit awaiting processing are different problems, and repeating the payment can create a second swap instead of moving the first one along.

The useful question is not simply “Is it pending?” It is “Which chain or protocol step is holding it?” Follow the transaction hash at the source, the status in the swap record, and any egress hash at the destination. That sequence shows what has happened and what remains.