124621 is an invalid block index (this is different from a block height)
Also, there seems to be a problem with the timestamp. Take for example the block 2016. The
rawdata shows the timestamp 1233063531, which corresponds to 27 Jan 2009 13:13:16, but in the
block page you show 2009-01-27 13:38:51.
I'll take a look at this, possibly my server time is out.
Thanks - nice site! Ben Reeves recently noted that it answered my 'Market capitalization over time' question at stackexchange:
http://bitcoin.stackexchange.com/q/2047/99But as I noted there I'm puzzled as to why the "unix time" timestamps for the daily data points in the json output aren't for midnight UTC. Why always 14:55:45 UTC for the market cap page, and 18:15:05 for transaction-fees, etc?
Also, for
http://blockchain.info/charts/transaction-fees can you stop rounding off the fees to the nearest BTC? It's just bouncing around near zero now.
And do you know why there is a huge increase in estimated transaction volume since Nov 16th, to all-time highs?
http://blockchain.info/charts/estimated-transaction-volumeFinally, can you put in a redirect from the original URL for the site (
http://pi.uk.com/bitcoin/...), so old examples posted here work?
I started generating data at odd times, not at midnight. Wow transaction fees have really plummeted I will adjust the rounding.
There was a ton of BTC moved around recently e.g.
http://blockchain.info/tx-index/12730431/8a4852cf51365059042d024eb0838ce14333b8de5d3c64394459bfac38a73a24 i think that is what has could the spike.
Redirect from pi.uk.com should be up.
I've got a ton of good suggestions from people but not much time to implement them so apologies if I don't get round to them right away. Got a great new feature coming out sometime this week which will make using bitcoin easier for a lot of people.