You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm encountering a problem with visualizing the second chart titled "Transaction vBytes per second (vB/s)" on https://mempool.space/testnet/graphs/mempool. When the "Cap outliers" toggle is turned on, the graph displays with the y-axis maximum set to 129 vB/s:
Description
Hi, I'm encountering a problem with visualizing the second chart titled "Transaction vBytes per second (vB/s)" on https://mempool.space/testnet/graphs/mempool. When the "Cap outliers" toggle is turned on, the graph displays with the y-axis maximum set to 129 vB/s:
**
![image](https://private-user-images.githubusercontent.com/3199720/324248653-f0901b47-663f-4ecb-971b-d179f9643fbc.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTg1MDY5MjYsIm5iZiI6MTcxODUwNjYyNiwicGF0aCI6Ii8zMTk5NzIwLzMyNDI0ODY1My1mMDkwMWI0Ny02NjNmLTRlY2ItOTcxYi1kMTc5Zjk2NDNmYmMucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDYxNiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA2MTZUMDI1NzA2WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YWJhZGExZTM2OGQ0MmM0YTE2Zjg1YTI1NzJiNmQ1NTZkOGM4ZDcwOGRmYjkyYmQ5M2RkODE1ZGRhZmUyODlkZCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.LAZkBKrcZcUM4-JkoA2gEUvv4f5ZnIIBSD6efR61hds)
**
Also the export/download shows a cut chart:
![incoming-vbytes-1y-1713703783](https://private-user-images.githubusercontent.com/3199720/324248779-30d724b5-741a-4add-baa3-6958d43c4bdd.svg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTg1MDY5MjYsIm5iZiI6MTcxODUwNjYyNiwicGF0aCI6Ii8zMTk5NzIwLzMyNDI0ODc3OS0zMGQ3MjRiNS03NDFhLTRhZGQtYmFhMy02OTU4ZDQzYzRiZGQuc3ZnP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDYxNiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA2MTZUMDI1NzA2WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZTFjYmUyNGM3NDNiOTFiNTU1Yjc4ZDA3NzBkZDcwY2E0MDU0MWNjNGRlZWU4Mzg3ODZjNzc4OTMwZWYwZmU5YiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.NQNUzAlnsBV9ABq8DPyCFBjTlUiwNeU3qXgIeEpXXHY)
Version
node202.fra.mempool.space (v3.0.0-dev) [bb44ed15][0708a2ba]
Device or machine
Chrome Browser 124.0.6367.60 64bit on Windows 10 Pro 10.0.19045
The text was updated successfully, but these errors were encountered: