Closed timothyylim closed 5 years ago
I tend to agree that the y-axis needs some work. But I don't like having just ["low", "high"]. Doesn't really give that more information. Additionally there are usually more low-feerate-tx than high-feerate-tx. Showing a user a transaction between low and high on a non-linear graph seems to be only making things harder to understand.
Would having the y-axes as feerate solve a similar problem?
An example would be having e.g. ["1s/byte", "10s/byte", "50s/byte", "100s/byte", "
What do you think?
I've done some work on this. Bit different that I first though, but I think it gets the job done without removing the y-axis labels. It's currently live on https://dev.mempool.observer.
What do you think?
Elegant. It was what I wanted and it keeps clutter to a minimum. Well done :)
Since the mempool can be considered a queue of transactions and since we sort them by transaction fee, it makes sense to present it to the user as a sort of priority queue.
It doesn't really matter to users exactly how many transactions there are in the mempool but instead, where their transaction is in relation to the others.
I suggest relabelling the y-axis as:
the 'high' label will obviously be at the top of the axis when coded up.