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
One feature I am missing from the old cubedro ethstats implementation is the pending transaction count on each node. During stress testing of networks, I find this number useful to see how quickly my node is working through its transactions, and if any transactions are currently stuck in its pending pool.
Acceptance Criteria
A new column should be added for "pending transactions" showing how many transactions exist on a node that have not yet been relayed to the network.
The text was updated successfully, but these errors were encountered:
Feature Request
One feature I am missing from the old cubedro ethstats implementation is the pending transaction count on each node. During stress testing of networks, I find this number useful to see how quickly my node is working through its transactions, and if any transactions are currently stuck in its pending pool.
Acceptance Criteria
A new column should be added for "pending transactions" showing how many transactions exist on a node that have not yet been relayed to the network.
The text was updated successfully, but these errors were encountered: