If getrawmempool size is >0 for more than a few minutes, it could mean large zxtns with low fees that are waiting to be included in a block. Currently, the UI does not show a count of pending xtns at all, the user has no idea how many are pending or how long they have been pending without manually digging into the data, which almost nobody will know how to do.
We should at least render a count in the hushd tab for debugging and think how we can tell average users about this information in a way that is useful to them.
If `getrawmempool` size is >0 for more than a few minutes, it could mean large zxtns with low fees that are waiting to be included in a block. Currently, the UI does not show a count of pending xtns at all, the user has no idea how many are pending or how long they have been pending without manually digging into the data, which almost nobody will know how to do.
We should at least render a count in the hushd tab for debugging and think how we can tell average users about this information in a way that is useful to them.
If
getrawmempoolsize is >0 for more than a few minutes, it could mean large zxtns with low fees that are waiting to be included in a block. Currently, the UI does not show a count of pending xtns at all, the user has no idea how many are pending or how long they have been pending without manually digging into the data, which almost nobody will know how to do.We should at least render a count in the hushd tab for debugging and think how we can tell average users about this information in a way that is useful to them.
This still seems like a good stat to add for debugging purposes to what is now called the "Node Info" tab