Check the nonce before you submit a bridge transfer

1 is the number of transactions with a given account nonce that can execute from your wallet on one chain. A bridge transfer starts with a transaction on the source chain, where that nonce can conflict with another pending transaction from the same account. Check which transaction is holding the nonce before you submit again, or your new transfer may simply wait behind it.

What does a nonce conflict mean for a bridge transfer?

A nonce conflict usually means your wallet has signed or broadcast two source-chain transactions with the same account nonce. The network can include only one of them; if one is still pending, the other is an alternative, not a second independent transfer.

This can happen if you click submit twice, use two wallet apps at once, or submit another transaction while an earlier one is stuck. The bridge’s route and destination do not change this source-chain rule. For a fuller explanation of how to choose a super bridge route, see this guide to choosing a super bridge route; route selection is a separate decision from resolving a pending wallet nonce.

Is a wallet nonce the same as a bridge message nonce?

No. Your wallet’s account nonce orders transactions sent by your address on a specific chain. A bridge message nonce, where a protocol uses one, identifies or sequences messages handled by its contracts; its exact purpose depends on that bridge’s design.

These counters can both appear in status pages or explorers, but they are not interchangeable. A source transaction can be confirmed while its bridge message is still waiting for verification or delivery. Conversely, a wallet-level nonce problem can prevent the source transaction from confirming at all.

What should you check before submitting again?

First, inspect the source-chain transaction in your wallet or a block explorer. Check its status and nonce, then compare it with the next nonce shown for your address. Wallets can disagree about pending transactions because they may rely on different node views.

• If the original transaction is pending, wait or use the wallet’s speed-up option if available.
• If it is confirmed, check the bridge’s own status before starting another transfer.
• If it failed, confirm whether the source-chain fee was still charged and whether the bridge records any message.
• If another transaction used the same nonce, verify which one was included before taking further action.

Speeding up generally means broadcasting a replacement transaction with the same nonce and a higher fee; it does not mean the original and replacement will both execute. A cancellation attempt is also a competing transaction, and it may not succeed if the original has already been included.

When is it safe to retry the bridge transfer?

Retry only after you know what happened to the first source transaction. If it confirmed, follow that transfer’s bridge status rather than submitting another one. If it failed or was replaced, make sure the bridge did not accept the message before starting a fresh transfer.

Keep the source chain, transaction hash, wallet address, and bridge status together while you investigate. The practical rule is simple: resolve the source transaction first, then decide whether the bridge action needs a new submission.