softsimon

Wait. So this is not supported by the latest official Bitcoin Core 25.0?

We solved this by removing the "rainbow" from the dashboard and replaced with the next block visualization. The full mempool graph is on it's own graph page where it makes...

- [x] Merge new init-api to master - [x] Go through all pages and make sure they are pre-renderable (fix document, window, setTimeout etc) - [ ] Make unique URLs...

> the accelerate button should always appear, this is the actual bug Appear, but being disabled? Or what is the point of showing it. The ability to accelerate again?

Been fixed

This seems related to this feature https://github.com/mempool/mempool/issues/4839 After transaction, addresses is next thing. The floating "popup" could be expanded to this full page overview thing.

A question regarding the "Backend syncing" part. It seems the blocks will now flow from left to right even though the mempool is not matching with null as match rate?...

I've seen it when going back from offline / switching back to the session. It's probably an arrow thing, the transaction you're checking is probably in another block.

Getting a slight change in `effectiveFeePerVsize` calculation from the backend with this PR From ` "effectiveFeePerVsize": 6.966216216216216,` To ` "effectiveFeePerVsize": 6.989830508474577,` Is that fine?

2nd bug, we already prevent graph entries before the mempool is fully in sync. So no idea what went on here.