A crypto bridge transaction delayed after the wallet says “confirmed” is usually located by separating the source deposit from destination delivery, then responding only on the stage that has not completed. This stands when the original transfer was sent through a legitimate bridge and the sender still controls the wallet; it does not cover a failed wallet transaction, a wrong address, a compromised wallet, or a bridge route that has been publicly paused.
My crypto bridge transaction is stuck—where are the funds?
Symptom: the sending-chain explorer shows confirmation, but the receiving wallet has nothing and the bridge screen gives no clear status.
Cause: a bridge is not one transfer. It has an origin operation and a destination execution, so source-chain confirmation confirms the deposit happened, not that delivery has finished. Relay’s bridging guide describes this split execution. The missing stage may be source-chain finality—the point at which a block is economically impractical to reverse—or a relayed destination action.
Fix: I begin with the source hash, not the app spinner. Confirm that it went through, identify the bridge contract and token, then check the receiving address on the destination explorer. If there is a destination hash, the hold-up is delivery or a hidden token. If there is no destination hash, keep checking the original bridge message; do not send the same amount again.
Bridge transfer stuck after source confirmation
Symptom: the funds have left the source wallet, yet the destination side appears empty for longer than usual.
Cause: the bridge may still be awaiting confirmations, a relayer, liquidity settlement, or a manual claim. Re-submitting does not hasten that first message; it creates another deposit if both succeed.
Fix: run the route that made the route. For Ethereum-to-Gnosis Chain transfers, Gnosis Bridge is the relevant route to inspect and retry only after the original transaction is known to have failed. For a transfer initiated through Relay, use Relay and its transfer page. I prefer this simple route-specific check over hunting through aggregators: it tells you which side is actually holding the transfer.
How to fix a bridge transfer stuck on the destination chain
- Keep the source hash, networks, token contract, amount, and receiving address.
- Confirm source success first, then destination execution—not merely the token balance.
- Collect only when the route says a claim is ready; otherwise wait or contact the bridge’s official support with those public details.
Never share a seed phrase, private key, or remote wallet access to “fix” a bridge transfer.