If the transaction is still pending, open its details in MetaMask and use Cancel when available. Cancellation attempts replace the original transaction and can require a network fee. A transaction already confirmed cannot be undone this way. Check the explorer before acting.
Establish whether anything remains to cancel
Open the account and network used for the original request. Find the transaction details and explorer link. A wallet label can lag behind the network, so inspect the actual hash before relying on an old Pending status.
If the transaction succeeded, cancellation through replacement is no longer the appropriate mechanism. Read the asset movements to understand what completed. If it failed after inclusion, inspect the error and paid fee rather than trying to cancel an execution that already happened.
If the hash is not found, confirm the network and whether the application actually broadcast the request. A missing result on one explorer does not prove every network node has discarded it. Preserve the hash and any provider reference while investigating.
For an exchange withdrawal, the exchange controls its sending account. A receiving MetaMask wallet cannot cancel that provider's transaction. Use the exchange's internal withdrawal process and status definitions for that case.
Try the built-in Cancel path
- Open the original transaction's detail view while it remains pending. Check that the sender, network, and intended action are the ones you want to stop.
- Select Cancel if the current wallet version offers it. Read the replacement request and its fee instead of assuming cancellation is free.
- Approve only if you accept that cost and understand that the original can still win the race into a block.
- Keep both the original hash and any replacement hash. Monitor their status on the same network.
- Confirm which transaction used the nonce on-chain. A button click or submitted notification alone does not establish a successful cancellation.
Understand why the nonce matters
For an ordinary Ethereum account, the nonce sequences transactions from that account on that network. A replacement targets the same nonce as the original, with parameters the network accepts for replacement.
Transactions at higher nonces can wait behind an earlier unresolved request. Inspect the oldest relevant pending nonce first. Trying to fix a later transaction while ignoring the blocker may leave the queue unchanged.
A cancellation commonly uses a replacement that does not perform the original asset movement. If it confirms first, the original with the same nonce cannot also execute in that chain history. If the original confirms first, the cancellation cannot retroactively remove it.
Increasing a fee is a separate intention from canceling. A speed-up usually tries to preserve the original action with more competitive pricing. Choose the action that matches whether you still want the transfer or swap to happen.
Several hashes can therefore represent attempts to resolve the same nonce. Do not add all their quoted maximum fees as though they were separate confirmed payments. Inspect the receipt of the transaction that actually executed.
Manual replacement requires more care
MetaMask documents a custom-nonce method for situations where it is appropriate. Read the current instructions for your version, including any Smart Transactions setting that affects visibility of the nonce field.
On Ethereum, the documented idea includes sending a zero-value transaction to your own public account with the pending nonce and an acceptable replacement fee. This is an advanced repair action rather than a normal new transfer.
Verify the account, recipient, zero amount, nonce, and network individually. A new nonce can create another queued transaction instead of replacing the original. An incorrect recipient or nonzero amount can introduce an unintended payment.
Fee-replacement requirements and network conditions matter. Follow the wallet's current guidance rather than a fixed Gwei number from an old example. A higher quote still does not guarantee that your replacement reaches a block before the original.
If you cannot identify the pending nonce confidently, pause manual entry and consult official support material. Public identifiers can be examined without giving anyone your recovery phrase, private key, or remote access to the wallet.
Handle the rest of the queue after the result
When the blocking nonce is resolved, later transactions may become eligible to execute. Review them against your current intentions. A swap created earlier can still be waiting with terms you no longer wish to pursue.
If an application reports a canceled action but the explorer shows the original succeeded, use the on-chain result to assess the asset movement. Interface messages need to be reconciled with the confirmed record.
Clearing local activity or nonce data is a separate troubleshooting action. It does not delete a broadcast transaction from the network. Preserve the original identifiers and follow the provider's conditions before changing local records.
If the replacement itself fails during execution, inspect its receipt and the nonce result. A failure after inclusion can still consume a nonce and incur a fee. The relevant question is which transaction became part of the chain and what effect it had.
Close the incident with evidence
Record the original purpose, hashes, nonce, final status, and actual fee. If the original moved assets, identify where they arrived. If the replacement prevented that action, verify the balance and any remaining queued requests.
A cancellation cannot revoke permissions granted by a different earlier transaction. If your concern involves a token approval or signed authorization, investigate that permission separately using the wallet's official tools.
If secret recovery material was exposed, resolving a pending transaction does not repair the exposed key. That requires a broader wallet-compromise response according to the actual exposure.
For an ordinary stuck transaction, a clear record prevents duplicate sending and unnecessary retries. Before creating the next request, establish that the task is still needed and use a fresh preview under current network conditions.
When reviewing the incident, separate timestamps supplied by the wallet from timestamps supplied by a confirmed block. They may describe different moments. Record when you requested a replacement and when the network included the eventual result, while acknowledging any missing broadcast information. This helps explain why a cancellation seemed successful in the interface before the final outcome was known. It also gives support a useful sequence without inventing a precise race between transactions that your records cannot establish. If you intend to try the original task again, review the full balance and queued instructions first so a fresh request does not duplicate an action still waiting.
Reader questions
Will cancellation return gas already paid for a confirmed transaction?
No. The pending-replacement process does not reverse a confirmed receipt or its execution charges.
Can I cancel a transaction someone else sent to me?
Knowing the receiving address does not give control of the sending account. Ask the sender about their supported options.
Does disconnecting the dApp cancel its pending transaction?
No. Connection permissions and a transaction already broadcast to the network are separate matters.