What to Check When a ParaSwap Transfer Is Delayed

When a ParaSwap transfer is delayed, check the source-chain transaction first: its status tells you whether the wallet request is still pending, succeeded or reverted. ParaSwap routes swaps to on-chain liquidity; a bridge transfer can also depend on a separate bridge or relayer. Those are different stages, so a delay in one does not identify a problem in the other. For more on expected timing, see this guide to ParaSwap bridge and swap times. Start with the transaction hash in the wallet or block explorer, then follow the stage that has not completed.

How do I tell whether the transaction is still pending?

A pending transaction has been broadcast but has not yet been included in a confirmed block. Open its hash in the explorer for the network where you sent it. If the explorer cannot find the hash, check that the selected network is correct and that the wallet actually submitted the transaction. A wallet spinner or an open confirmation window alone does not prove that a transaction was broadcast.

If the transaction appears as pending, inspect its nonce and fee fields. The nonce is the account’s transaction sequence number; a pending transaction can hold up later transactions from that account on the same chain. Network congestion or a fee too low for current demand can leave it waiting. Where the wallet and network support replacement transactions, “speed up” generally submits a transaction with the same nonce and a higher fee. It replaces the pending transaction if accepted. Check the wallet’s replacement details before signing.

Do not send a second swap simply because the first one is slow. If the first transaction later confirms, the second could execute too. A cancellation request is also a replacement transaction, not a reversal: it may fail to replace the original, and it cannot undo a transaction already included in a block.

What does a confirmed source transaction tell me?

A confirmed source transaction has been included on its origin chain. Read the receipt, not just the wallet’s activity label: a successful receipt means the transaction executed without reverting; a failed receipt means the requested on-chain operation did not complete. For a swap, check the token transfer events and the destination amount against the transaction details. A successful receipt does not by itself prove that a separate cross-chain transfer has finished.

If the transaction reverted, the explorer may show a reason, though decoded errors are not always available. Common causes include insufficient gas, a token approval that was not in place, or execution conditions that no longer match the submitted swap. The source token may remain in the wallet when execution reverts, but the transaction can still consume gas. Confirm the token balance and receipt before attempting another swap.

If the source transaction succeeded but the destination asset has not arrived, identify the bridge or cross-chain provider named in the transaction or route details. A bridge leg can require its own confirmation, message relay or destination-chain execution. Check the provider’s transaction status using the source hash or bridge reference. ParaSwap’s role in routing the swap does not make every later bridge step part of the same on-chain transaction.

What should I check if the destination token is missing?

First confirm the destination chain and wallet address. A token sent to the expected address on another network will not appear in the currently selected network’s balance. Then check the destination-chain explorer for an incoming transfer. If it is recorded there, the wallet may need the correct token contract added to display the balance; verify the contract address from a reliable source before adding it.

If no destination transaction appears, use the bridge provider’s status to distinguish a relay still in progress from a transfer that needs recovery. Do not repeat the bridge transaction or sign an unfamiliar “claim” request just because the interface has not updated. Recovery procedures are provider-specific. Use the provider’s official support channel if its status shows a failure or stays incomplete beyond its stated processing window.

When should I retry or contact support?

Retry only after the first transaction’s state is clear. A reverted transaction can usually be submitted again after resolving its cause, but the new attempt gets a fresh quote and may execute at a different rate. If the first transaction is pending, decide whether to wait, replace it through the wallet, or cancel it; do not treat a new swap as a replacement. If it succeeded, investigate the destination leg or wallet display instead.

Before contacting support, gather the transaction hash, source and destination networks, sending address, token contract and the status shown by each relevant explorer or bridge tracker. Share these details only through the service’s verified support channel. Never provide a seed phrase or private key; transaction diagnosis does not require either.

The confirmed facts are the source transaction’s receipt and any destination-chain transaction. A bridge status can show whether a relay or claim remains outstanding. Until the destination transaction is confirmed, arrival is unverified; a pending label or missing wallet display alone does not establish that funds are lost.