Kanos pool rocks
Now how can the chinese explain this:
Height Age Transactions Total Sent Relayed By Size (kB)
388048 13 minutes 1 25.00 BTC F2Pool 0.26
388047 8 minutes 1494 27,450.82 BTC 21 Inc. 974.65Lol 2 blocks 5 minutes apart, and in that 5minutes they were unable to put even a single other transaction in the block other than claiming their 25 pieces of silver
And there still is that 12k transactions pending lol _D
Now that is either very very bad coding or done purposefully, 5 freaking minutes, you would think the slowest and lamest possible setup would be able to stuff some transactions in the block in 5 minutes..
Atleast kano.is stuffs em blocks proper..
The timestamp on the blocks is misleading, as should be evident by the fact it's reporting 048 older than 047
. I'm certainly not condoning the practice of mining empty blocks by any stretch of the imagination; however, if I look at my logs, I see those blocks reported only seconds apart:
2015-12-12 15:56:04 UpdateTip: new best=00000000000000000d8aea96e7533669d26afa88336d3306a9dd76ffc558d660 height=388047 log2_work=83.730241 tx=97301155 date=2015-12-12 16:01:37 progress=1.000003 cache=0.1MiB(0tx)
2015-12-12 15:56:07 UpdateTip: new best=000000000000000005a0ef1ce8303606ced29e26ee16f088a7bf1e4f485eaf8e height=388048 log2_work=83.730272 tx=97301156 date=2015-12-12 15:56:02 progress=1.000000 cache=29.2MiB(4765tx)
As you can see, for whatever reason, the date reported for block 388047 is later than the date reported for 388048. However, they were seen by my node 3 seconds apart from each other.