Speeding up a pending swap without creating a second trade

A wallet’s speed-up action generally creates a replacement with the same account nonce and a higher fee bid. The goal is to get the existing action included sooner, not to create an additional trade.

MetaMask documents this same-nonce behavior. Only one transaction for that sender and nonce can be included in the canonical account sequence.

Review the existing action first

Confirm it is still pending. Then check the swap’s deadline, token contracts, input and intended recipient. A higher fee does not repair expired transaction data or change a minimum output that the route can no longer deliver.

If the quote is no longer acceptable, speeding up may be the wrong decision. Cancelling and creating a newly reviewed swap is a different flow.

Track the replacement

Save the new hash and check which transaction confirms. The original can still win the race if it was included before the replacement reached the relevant builder or node.

Do not assume the fee shown for the original plus the replacement represents two final swap fees. Pending estimates are not settled charges. Inspect the receipt of the transaction that actually included, while accounting separately for any other confirmed actions.

If the wallet reports replacement underpriced, inspect the newest pending replacement rather than repeatedly pressing Speed up. If the transaction already confirmed, stop trying to replace it and verify its result. A successful speed-up means faster inclusion of the instructions you already signed, which can still succeed or fail on their contract conditions.