Skip to content

Change the status of pending txs to oudated based on sender's nonce #53

@0xmdh

Description

@0xmdh

Hi!
The explorer shows 2 transaction stuck forever yesterday (can't be mined because nonce 542 and 544 were already used after script re-run),
both of them are in status pendingg in rsk explorer, but can't be found in blockscout
1)
https://explorer.rsk.co/tx/0xeac0103b97a5a35685f09ffd868067196d8eb8f1c8a44e0a054ceec1cee81cc0
https://blockscout.com/rsk/mainnet/search?q=0xeac0103b97a5a35685f09ffd868067196d8eb8f1c8a44e0a054ceec1cee81cc0
2)
https://explorer.rsk.co/tx/0xba5818a971cfc420b953232af3e290b4eff9b1e25cb9023425ab59213f01f141
https://blockscout.com/rsk/mainnet/search?q=0xba5818a971cfc420b953232af3e290b4eff9b1e25cb9023425ab59213f01f141
These txs were left in the node's rsk explorer mempool but they will never be mined, they sould be removed from the mempool and would not see them again in the RSK explorer.
The strange thing is that the tx is still showed as pending in the RSK explorer and has not disappeared already, but it should.
So the issue is in the explorer?
It shouldn't last that long. Each node has a parameter of: after X time the pending transactions are removed. And that time X is just a few minutes that you remember. So, either some node associated with the explorer has a very high X OR THE EXPLORER on his account is sent to remember that transaction as pending, and does not release it again.
What should be seen is if there are transactions with the same sender and nonce, which were mined, and these, as similar transactions that competed with those, were the ones that lost.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions