A stuck bridge transfer calls for a chain-by-chain check

Recovering a stuck bridge transfer starts with tracing its source transaction and finding which cross-chain step has not settled. A pending label alone does not show whether funds are still confirming, waiting for a relay, or ready for a separate claim.

• Record the source transaction hash and sending address.
• Check the source explorer for a successful receipt and any bridge event or message ID.
• Check the destination explorer for a matching transaction, token, and recipient.
• Read the route’s status and instructions before retrying or submitting a claim.

How do you find where the transfer stopped?

Start with the source chain, where the signed transaction either failed, remains pending, or completed. If it reverted, the transfer did not proceed, though the failed transaction may still have consumed gas.

If it succeeded, follow the bridge’s message or transfer ID through the route’s own status page and the destination explorer. For the route-specific distinction between native and independent bridges, see the manta bridge guide; it explains why identifying the route changes what recovery options exist.

When can you retry, claim, or replace a transaction?

A source transaction that is still unconfirmed may sometimes be sped up or replaced with a wallet transaction using the same nonce. That affects only the pending source transaction; it cannot undo a confirmed deposit or withdrawal.

After the source transaction confirms, check whether the route is still relaying or requires a destination action. Some withdrawals need a separate proof or claim after a protocol-defined wait, while other routes settle automatically. Use the route’s own status and instructions to tell which applies.

Do not submit a second bridge transfer just because the first is delayed. The first message may still complete, leaving two transfers in flight.

What information should you give support?

Send the route’s official support channel the source hash, destination address, both networks, token contract, and any message ID. Include the status shown by each explorer and the time the source transaction confirmed.

Keep recovery on the original route unless its documentation directs otherwise. Never share a seed phrase or private key; legitimate support can investigate with public transaction details, but cannot reverse a confirmed on-chain transaction.