A cross-chain transfer usually has at least two chain events: the source transaction and delivery on the destination. Check which one is missing before you retry; a wait of 10 minutes alone does not prove the transfer failed.
1. Confirm the source transaction reached the chain
First, check the source transaction hash in that chain’s block explorer. If it is still pending, the bridge may not have received the funds yet; if it failed or reverted, the transfer did not begin as intended. A confirmed source transaction means the funds left your wallet, but it does not by itself prove they arrived on the destination.
For example, if you send ETH through a route that delivers a different token on Arbitrum, check the ETH transaction first. If it succeeded, keep that hash and use the route’s status information to follow delivery. If you want to move assets across chains and swap into a destination asset in one flow, ParaSwap handles that combined bridge-and-swap task.
2. Identify whether delivery or a swap is still underway
A confirmed source transaction can be followed by a wait while the bridge verifies it and a relayer submits the destination transaction. Some routes also require a destination swap, which can fail or take longer even after the bridge has delivered the input asset. The same distinction matters for a ParaSwap transfer: source confirmation and completed delivery are separate states.
Use the transfer record or route status tied to your source hash, then check the destination wallet for the expected asset. Timing depends on the chains’ finality, congestion, and the bridge’s verification design; a route that normally takes minutes can take longer during congestion or when it uses a longer security window. Don’t send a second transfer just because the destination balance has not changed yet.
3. Retry only when the original transfer cannot complete
Retry only after you establish that the first transfer failed, was refunded, or has no pending delivery path. If the source transaction succeeded and the route still reports delivery in progress, a second send can create a second transfer and a second set of costs.
Check whether the source funds remain in your wallet, whether the destination asset appeared, and whether the route reports a failure or refund. Bridge and swap routes may involve source-chain gas, a bridge charge or price impact, and destination-chain gas; the amount depends on the route and network conditions. If the source transaction failed, you may need to submit it again and pay source gas again.
I would wait when the source transaction is confirmed and delivery remains active; I would retry only after a clear failure or refund. If you need the funds urgently, or the route has no traceable delivery status, choose a route with a status you can verify before sending.
Top comments (0)