Pending Ethereum Transaction: Check Before You Send Again

Before sending again, check the original transaction on the correct network. A wallet’s pending label can mean a transaction awaiting inclusion, a transaction queued behind another, or activity that the wallet has not refreshed. Repeating the payment can create a separate transaction that executes later.

This checklist covers ordinary transactions from a regular Ethereum Mainnet account, also called an externally owned account or EOA. Smart accounts, private transaction services or bundles, bridge transfers and exchange withdrawals need their own provider’s instructions. If you did not submit from an account you control, do not try to replace the sender’s transaction yourself.

Start with the network and the full transaction hash

You can diagnose the first part without connecting a wallet or signing anything. Open the sending wallet’s transaction details and record these items:

1. Network: confirm Ethereum Mainnet. An Ethereum-style address on another chain does not make its transaction a Mainnet transaction.
2. Transaction hash: copy the whole transaction ID, not the recipient address. Use the wallet’s explorer link and verify its destination is the intended explorer.
3. Sender: compare the complete From address with your sending account. Also check the recipient and the intended action.
4. Nonce: find this transaction’s sequence number in its details. Record it with the hash, since a replacement has a different hash but uses the same sender and nonce.

Ethereum’s transaction documentation identifies the sender, recipient, value, input data and nonce as separate fields. A transaction to a contract may perform an action rather than simply pay the address shown in To. Check decoded details where available; do not assume every transaction is a plain ETH transfer.

Keep the original hash even if your wallet offers a retry button. It gives you a specific record to revisit instead of relying on a changing balance or a notification that disappears.

Read the status before choosing a fix

On the explorer, look for the status and block information together. Etherscan describes pending as waiting for inclusion in a block. Low fees and busy periods can contribute to the wait, but the word pending alone does not identify the cause.

What the record shows	What to check next
Pending, without a containing block	Check the sender’s earlier unresolved nonces before considering a replacement.
Success, with a block	Inspect the action and resulting state. Repeating the payment may duplicate it.
Failed, with a block	Read the failure reason. Waiting or speeding up that included transaction will not make it succeed.
Dropped and replaced	Follow the replacement hash and inspect its status and action.
Hash not found	Recheck the network and full hash, then compare wallet activity with the sender’s explorer history.

A failed transaction is not the same as one still waiting. The receipt status specification records execution success or failure; a failed execution can still have been included in a block. Gas consumed during execution is charged even if the action fails, as Ethereum’s gas guide explains. Diagnose the error before authorizing a new attempt.

For readers checking data through software, the JSON-RPC receipt documentation says pending transactions have no receipt. A returned receipt includes its block and status. In the raw JSON-RPC response, 0x1 means success and 0x0 means failure (the values 1 and 0). A missing receipt by itself does not establish where the transaction is: check that the provider knows the hash and is querying the right network.

A hash not found in one explorer is an unresolved observation, not proof that the transaction can never execute. Allow for propagation and indexing, recheck the wallet’s submission details, and use official wallet help if the records remain inconsistent. Do not create a second payment just to test the display.

Find the first unresolved nonce in the queue

Transactions from an ordinary account use a sequence. Suppose you find pending transactions with nonces 42, 43 and 44, and the earlier sequence has already been included. This is an illustration, not a live account. Nonce 42 is the first item to investigate; increasing the fee for 44 does not remove the earlier gap.

Open the sender’s activity on the same network and compare it with the wallet’s pending list. Check whether the earliest unresolved nonce is still pending, already included, or associated with a replacement hash. Do this for the same sender account, not every account visible in your wallet.

Etherscan’s replacement explanation shows replacements sharing the original sender and nonce. An earlier nonce must be consumed by an included transaction before later ones can execute. A failed transaction included in a block also consumes its nonce: the protocol’s transaction rules increment the sender’s nonce before execution. Do not keep trying to replace a nonce already used on chain.

Once the first gap is resolved, revisit later queued transactions. They may still represent actions you no longer want. Clearing the first obstruction is not a decision to approve every item behind it.

Waiting, speeding up and cancelling are different choices

If the transaction remains pending and you still want the action, waiting may be acceptable. There is no universal deadline after which every Ethereum transaction automatically fails. Compare the current status and fees with your need to complete the action.

A wallet’s Speed up flow attempts a replacement with the same nonce and a higher fee. Cancel also attempts a replacement; it does not erase a signed instruction from the network. The original can be included first. An included cancellation transaction costs gas, so cancelling is not a free undo operation.

Follow your wallet’s current official instructions. MetaMask’s guide provides its supported controls and explains the nonce relationship. Read the confirmation’s network, account, action and fee before deciding to sign. Use current estimates rather than copying a fee number from an old screenshot. This checklist does not supply a universal fee multiplier or guarantee inclusion.

A normal Send operation with a fresh nonce is not a replacement just because the recipient and amount match. Keep both hashes if you have already retried, and establish each record’s status before taking another action.

For ordinary transactions where you fund the fee yourself, check native ETH on Mainnet. A token or combined portfolio total does not establish the gas balance; our ETH and WETH guide explains that distinction.

A wallet reset changes local history, not Ethereum

If the explorer shows inclusion while your wallet still says pending, refresh or reopen the wallet and recheck the exact hash. If the discrepancy persists, consult official support with the network, public sender, hash and nonce. Keep that record before changing local activity.

MetaMask’s reset guidance limits this troubleshooting step to cases where support instructs it and the transaction is not visible in the explorer. Clearing activity and nonce data removes the wallet’s local knowledge of transactions. It does not cancel a transaction already broadcast, and account reset is different from resetting the entire wallet.

Finally, an unchanged portfolio balance does not prove failure, and a lower balance does not identify which transaction executed. Fees, other activity and delayed data can affect the comparison. Use the balance mismatch checklist after checking the transaction record. Before any new signature, you should be able to name the network, sender, original hash, nonce and observed status, including any replacement.