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
Whenever I am performing a tx when I have another one pending, I can see the Information display saying I have a pending tx. However, if I have speed up/cancelled that transaction I see how the number of pending transactions increases, even though the speed up/cancel tx's all have the same nonce, meaning just 1 is actually pending
Expected behavior
Possibly transactions with the same nonce should count as 1 pending tx instead of adding up to the queue? Similarly as what we do in the Activity list (all same nonce tx's are consolidated into 1)
Screenshots/Recordings
pending-tx-count.mp4
Steps to reproduce
Start a tx with low nonce
Trigger speed up/cancel several times
Start a new tx
See as many pending tx's as performed in step n1 + n2
Error messages or log output
No response
Version
11.15.4 prod might be earlier too
Build type
None
Browser
Chrome
Operating system
Linux
Hardware wallet
No response
Additional context
No response
Severity
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
Whenever I am performing a tx when I have another one pending, I can see the Information display saying I have a pending tx. However, if I have speed up/cancelled that transaction I see how the number of pending transactions increases, even though the speed up/cancel tx's all have the same nonce, meaning just 1 is actually pending
Expected behavior
Possibly transactions with the same nonce should count as 1 pending tx instead of adding up to the queue? Similarly as what we do in the Activity list (all same nonce tx's are consolidated into 1)
Screenshots/Recordings
pending-tx-count.mp4
Steps to reproduce
Error messages or log output
No response
Version
11.15.4 prod might be earlier too
Build type
None
Browser
Chrome
Operating system
Linux
Hardware wallet
No response
Additional context
No response
Severity
No response
The text was updated successfully, but these errors were encountered: