I've thought about this a bit before. Originally I wanted to include the entire mempool in the area below the dotted line, and make the page scrollable so you could explore the full depth of the pool. Unfortunately that introduces some UX challenges that I haven't quite figured out, and maintaining performance would also be tricky (at times of high congestion there can be tens of thousands of pending transactions, and theoretically the mempool can reach up to 300mb - that's a lot of data to process and render!)
But it's not impossible, and it's definitely on the roadmap if I can figure out a reasonable solution.
In the meantime, I'm considering some other approaches that might be a good compromise. Perhaps an extra panel with a simplified view of the whole mempool, with lower data/graphics requirements than the main visualization.
At the very least I plan to add some more basic mempool data to the UI like memory usage, fee statistics etc.
Great suggestion, thanks!
I've thought about this a bit before. Originally I wanted to include the entire mempool in the area below the dotted line, and make the page scrollable so you could explore the full depth of the pool. Unfortunately that introduces some UX challenges that I haven't quite figured out, and maintaining performance would also be tricky (at times of high congestion there can be tens of thousands of pending transactions, and theoretically the mempool can reach up to 300mb - that's a lot of data to process and render!)
But it's not impossible, and it's definitely on the roadmap if I can figure out a reasonable solution.
In the meantime, I'm considering some other approaches that might be a good compromise. Perhaps an extra panel with a simplified view of the whole mempool, with lower data/graphics requirements than the main visualization.
At the very least I plan to add some more basic mempool data to the UI like memory usage, fee statistics etc.