Very nice! What accounts for the difference in the number of unique clients and the total of the clients by version?
One can only find out what version another node is running by connecting to them. The vast majority of hosts are behind a firewall and I cannot connect to them. I have to wait for them to connect to me. A couple additional hosts are already maintaining too many connections- like ~125- and aren't accepting more.
Nice statistics. Note that the number of BTC in transaction is less significant because people can send back and fro in short time. Instead it is better to show the graph of number of transaction vs time interval which will directly give information of the transaction waiting time distribution, which is expected to be Poison.
Such a chart would be more difficult for new users to grasp. Also it would never change and that would be a bit boring. I did consider it though. Similarly, it could be a line graph showing the percentage of transactions that were confirmed
by that time. For example- at 1 minute, the line might be around 10%. At 10 minutes, the line would be around 50%. And at 60 minutes, the line would be around 90%. It would get to 99.9% somewhere around 300 minutes (just a guess).
For the count page, the number of client is larger than expectation because its number should be of the same order of magnitude of miner, as they are always connect the the network, which should only be few ten thousand only. You may take a look of
http://bitcoinstatus.rowit.co.uk/ which shows that there is around 50k. Counting unique IP is not a good method because it is easier to change it occutionally.
I don't understand. Could you please elaborate? Or could someone else elaborate? Thank You.
Why does the graph on the transaction timer page start at -8.3? Shouldn't it start at 0? Or is it so you can better see those transactions which took less than a minute?
It makes it easier to see. If you drag a box to zoom in, it adjusts automatically.
Very nice service and good looking website! Can you make it so that we can look at transactions from longer periods than 4 hours? Maybe 24? Very nice all around though
That's a thoughtful suggestion. I actually did have it set at 24 hours originally, but the number of transactions- and thus data points- that occur over a 24 hour period is extremely high and is too much for browsers to render. You'll notice that when zooming, it is already slow. Though if more people would like that much data, I could add a button to view the 24-hour chart. In the future, as Bitcoin becomes more popular, if browsers cannot handle all of the transactions [chart data points] that occur in a 4 hour period, I will need to lower this value further.
