You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this example, I have a pending transaction with a nonce of 7. On mycrypto.com, I create a new transaction and set the nonce as 7 with a higher gas price, as shown in picture one. This transaction is completely unrelated to the current pending transaction at nonce 7. I am doing this intentionally because I no longer need the current transaction to go through. However, when mycrypto pushes the new transaction to metamask and I submit it, the transaction has now been changed to having a nonce of 8. Now, both transactions will be processed by the network instead of the second transaction taking miner preference (due to higher gas price) over the original.
While the side by side screenshot shows as confirmed now, the first transaction was pending at the time of submitting the second and for quite a while after. Also, the rejected transaction in the picture is not relevant to this discussion.
The text was updated successfully, but these errors were encountered:
In this example, I have a pending transaction with a nonce of 7. On mycrypto.com, I create a new transaction and set the nonce as 7 with a higher gas price, as shown in picture one. This transaction is completely unrelated to the current pending transaction at nonce 7. I am doing this intentionally because I no longer need the current transaction to go through. However, when mycrypto pushes the new transaction to metamask and I submit it, the transaction has now been changed to having a nonce of 8. Now, both transactions will be processed by the network instead of the second transaction taking miner preference (due to higher gas price) over the original.
While the side by side screenshot shows as confirmed now, the first transaction was pending at the time of submitting the second and for quite a while after. Also, the rejected transaction in the picture is not relevant to this discussion.
The text was updated successfully, but these errors were encountered: