A cross-chain swap can stay pending because each chain prices block space separately, so congestion on one network can delay a step in the transfer. The key is whether your source transaction is still unconfirmed or has already reached the bridge; that determines whether to raise its fee, wait, or check the destination.
Why can one busy chain hold up the whole swap?
A cross-chain swap is a sequence of actions, and each action depends on the one before it. Your wallet first submits a transaction on the source chain; after that transaction is confirmed, the bridge route can arrange the destination-side action. A delay at either end can make the overall swap look stuck.
Each chain has its own fee market. On Ethereum, users compete for block space by including a priority fee, while the base fee adjusts with block demand. If the source transaction’s offered fee is too low for current demand, it may wait. Destination-chain congestion can also delay the final transfer or token exchange, even after the source transaction has completed.
Layer 2 networks can add another wrinkle: a transaction may pay for execution on the layer 2 and for data posted to Ethereum. Those costs do not always rise together. A quiet layer 2 can still become more expensive if posting data to Ethereum gets costly.
What should I check before changing anything?
Check the source transaction hash in that chain’s explorer first. If it is still pending, the bridge may not have received a confirmed deposit or instruction yet. If it is confirmed, look up the bridge route’s status to see whether it is waiting for a relay or destination execution.
A wallet that says “pending” without a transaction hash may not have broadcast the transaction at all. Recheck the wallet and network before submitting again. If the transaction is confirmed but the destination token has not arrived, use the route’s status page or support process to check whether a retry is available.
Fees are only one part of the cost. Include source gas, any bridge or relayer charge, destination execution gas, and the effect of price movement while the swap waits. For a route that bundles a transfer and token exchange, the fermi swap fees can help you review the route costs before you start.
Should I speed up the transaction or wait?
If the source transaction is pending, raising its fee may help it get included sooner. On Ethereum, a wallet may offer “speed up” by replacing the pending transaction with one using the same nonce and a higher fee. The replacement must meet the network’s fee rules, and the wallet should handle those details.
For example, suppose a transaction uses 150,000 gas units. At an illustrative total fee of 30 gwei, it costs 0.0045 ETH; at 90 gwei, it costs 0.0135 ETH. That extra 0.009 ETH buys a chance of faster inclusion, not a guaranteed completion time. Compare it with the cost of waiting and with the value of getting the swap done now.
If the source transaction is already confirmed, raising its fee cannot accelerate a bridge relay or destination transaction. Wait for the route’s stated processing window, then check whether destination gas or a retry is holding things up. When comparing a fermi swap quote with another route, check which chain’s gas estimate it covers and whether destination execution is included.
How do I choose a better time next time?
Compare the complete route cost at the time you are ready to submit, then decide whether the saving from waiting is worth the risk of a price change. Fee trackers can show recent gas levels, but a low reading is not a promise: a block can fill quickly, and destination fees may follow a different pattern from source fees.
For instance, if you are sending USDT from Ethereum and the source fee is unusually high, you can wait before signing or submitting, then refresh the quote. If you have already submitted and the transaction is pending, a better fee later does not make the original transaction cheaper; it only helps you decide whether to replace it or let it continue.
Where a route uses Axelar or another relay, the source confirmation, relay processing, and destination execution are separate stages. A confirmed source transaction can therefore coexist with a transfer that is still processing. Record the source hash and route identifier so you can tell which stage needs attention.
What should I do now?
Use this short checklist to choose the next step:
- Find the source transaction hash and check whether it is pending, confirmed, or failed.
- If it is pending, compare the offered fee with current chain demand before using the wallet’s speed-up option.
- If it is confirmed, check the bridge status and destination chain; do not submit the same transfer again without checking its state.
- Before a future swap, compare total route costs and refresh the quote just before submitting.