How to Check If an Avalanche Bridge Transaction Is Stuck in the Mempool

13 November 2026

A transaction is stuck in the mempool when the Avalanche Bridge has submitted it to the source chain (usually Ethereum) but it has not been mined into a block. You can check this by looking up the transaction hash on the source chain’s block explorer, examining its status and gas parameters, and then using the Avalanche Bridge interface or a third-party tool to confirm whether the bridge’s relayer has picked it up. If the transaction remains unconfirmed for an extended period, it is likely stuck due to low gas or network congestion.

What “Stuck in the Mempool” Means for an Avalanche Bridge Transaction

The Avalanche Bridge works by locking assets on one chain (e.g., Ethereum) and minting wrapped versions on Avalanche C-Chain. The user initiates a transaction on the source chain. That transaction must be confirmed by the source chain’s network before the bridge’s relayer can proceed. Until that confirmation, the transaction sits in the mempool - a pool of pending transactions waiting to be mined.

Common causes for a stuck transaction: - Gas price set too low for current network conditions. - Nonce value that is out of order relative to other pending transactions from the same wallet. - Source chain congestion, especially on Ethereum mainnet during high activity.

Step-by-Step: how to check if your transaction is stuck

1. Find the Transaction Hash

The transaction hash (TXID) is the most important identifier. You can get it from:

• The Avalanche Bridge interface after you initiate the transfer. The bridge usually shows a link to the source chain explorer.
• Your wallet’s transaction history (MetaMask, Ledger, etc.). Look for the outgoing transaction on Ethereum (or the source chain).
• A block explorer search using your wallet address.

If you cannot find a transaction hash at all, the bridge may not have submitted the transaction yet. Check your wallet for any pending signature requests or errors.

2. Look Up the Transaction on the Source Chain Explorer

Go to the block explorer for the source chain (e.g., Etherscan for Ethereum, or a C-Chain explorer if bridging from Avalanche). Paste the transaction hash into the search bar.

What to look for:

• Status: If the transaction shows as “Pending” or “Queued,” it is still in the mempool. If it shows as “Success” or “Confirmed,” it has been mined - the problem is elsewhere. If it shows as “Failed” (red), the transaction was processed but reverted.
• Gas Price: Compare the gas price you set to the current network gas price. If yours is significantly lower, the transaction may never be mined unless you replace it.
• Nonce: Check the nonce number. If you have other pending transactions with lower nonces from the same wallet, those must be confirmed first. A stuck transaction with a high nonce will wait indefinitely.

3. Check the Avalanche Bridge Interface or Dashboard

Some versions of the Avalanche Bridge show the status of active transfers. Look for a “Pending” or “In Progress” section. If the bridge’s relayer has not seen the source chain confirmation, it may show a waiting state or a timeout countdown.

You can also use the Avalanche Bridge’s “Transaction History” feature if available. Enter your wallet address to see all recent bridge attempts and their current statuses.

4. Use a Third-Party Mempool Tracker (Optional)

For Ethereum-based transactions, you can use sites like Etherscan’s “Pending Transactions” page or a mempool visualizer (e.g., TxStreet). Paste your transaction hash to see if it is still in the mempool, its position in the queue, and whether it is being broadcast by nodes. This is not necessary but can give you a visual confirmation.

5. Determine If the Transaction Is Stuck vs. Delayed

A transaction is considered stuck if it remains pending for longer than typical for the source chain under current conditions. On Ethereum, a pending transaction for over an hour during normal congestion is stuck. During a gas war, it may take longer.

If the transaction has been pending for more than a few hours without any movement, it is likely stuck. If it has been pending for only a few minutes, it is probably just waiting for the next block.

What to do if it is stuck

This page is about checking, not fixing, but knowing the options helps you decide whether to wait or act.

• Speed up: If your wallet supports it, you can resend the same transaction with a higher gas price (replace-by-fee or RBF). This replaces the old transaction in the mempool.
• Cancel: Send a zero-value transaction to yourself with the same nonce and a higher gas price. This cancels the original transaction.
• Wait: If gas prices are volatile, the transaction may eventually be mined when network activity drops. There is no guarantee.

For the Avalanche Bridge specifically, if the source chain transaction fails or is never confirmed, the bridge will not proceed. You will need to retry the bridge operation from scratch. The bridge does not lock funds until the source transaction is confirmed, so your assets remain in your wallet until that point.

How to Avoid Getting Stuck in the Future

• Set gas prices based on current network conditions. Use a gas estimator (e.g., Etherscan Gas Tracker) before submitting.
• Keep your nonce in order. Avoid sending multiple transactions from the same wallet without waiting for confirmation.
• For time-sensitive bridges, consider using a third-party bridge that offers faster finality or higher gas tolerance, but be aware of the trade-offs (covered in “Avalanche Bridge vs Third Party Bridges for Moving Ethereum Assets”).
• Monitor the source chain’s status. If it is congested, delay your bridge attempt.

Summary

To check if an Avalanche Bridge transaction is stuck in the mempool: locate the transaction hash, look it up on the source chain’s block explorer, and confirm it shows as pending with low gas or an out-of-order nonce. Use the Avalanche Bridge interface to see if the relayer has acknowledged the transfer. If the transaction remains pending beyond normal timeframes, it is stuck. At that point, you can attempt to speed it up, cancel it, or wait - but the bridge will not complete until the source transaction is confirmed.

Back to avalanche