Jul 6, 2025

Very cool -- how are you getting the data -- straight from the db?

No im getting the data from the event.log file for now. In the future the data will be directly sent from the node via websockets to the dashboard.

This is looking really good Rowan. I think it would be worth splitting the header events into their own plots, since these are so rapid initially, and so infrequent later, that they get completely buried the block plots. Also, it might be interesting to see downloaded and validated blocks in the pie chart. Downloaded will always be <= to validated which is always <= confirmed. But unlike confirmed, these are not sequential. You would have to maintain a count. That would be fine unless the node is restarted with partial completions of download/validate, since you wouldn't have an accurate count. But it's also the case that a validated block implies that all blocks up to that height are downloaded, and a confirmed block implies all blocks up to that point are validated. So you could correct quickly.

Correction. Downloaded can be any amount ahead of validated (up to the window size), and validated can be any amount ahead of confirmed. Not <=. But the rest is correct.

You are able to deselect any event that you don't want to see on the graph and the graph will resize to fit the data. Do you still think it is worth it to make a separate graph. Because the way I see It most of the time the user would just keep those deselected and when they are interested in that data they can select it. But I can totally see wanting them to just exist in a separate graph if that is what you think is best and would be easy to change.

Ah, just leave that it's good. Does the plot continue to scroll right, and is there a way to scroll back or scale the x axis so that earlier periods can be observed?

Ya I want to implement that That is what ill do next