Nano TPS Historical Chart

So how does this work?

Each day nanotps.com checks the network's performance via a brief burst of activity. Blocks are broadcast all at once from a few thousand unique accounts, ensuring conditions are as favorable as can be. I've tried to make this analysis as fair and straightforward as possible.

How is TPS calculated?

To avoid underestimating the tps, the timer starts the moment the entire batch has been broadcast to all the nodes. We then wait for that many confirmations to occur, which may include blocks from real users. That way other people using the network won't change the results. Once we have our confirmations, we divide the batch size by the number of seconds that have passed. We then divide by 2 to get our final tps.

Why are some days so low?

Nano has suffered several attacks over its history. On days where nothing is happening, the tps can reach its highest values. But when an attacker actually tries to harm the network, performance has dropped dramatically. Usually there's some fixes a few months/years later, but in each case someone then takes the network down again. This is why I think it's really important to keep your nano on the exchanges.

What could raise these numbers?

Better hardware and fewer nodes. Nano's network overhead scales with the square of the number of PRs, so if you're delegating to a small or slow one, consider moving away. There is a security tradeoff in doing so, but if capacity is your goal, this makes sense. In the long term software updates and moving away from ORV may help as well.

What could lower these numbers?

A few GPUs spamming, the introduction of forks, and bandwidth cuts dramatically reduce throughput. Forks take substantially longer to resolve and can be generated faster than normal block spam since every side of a fork shares the same PoW. Those days where the graph reports numbers near zero are ones where an attacker was present.