After a profitable launch, Frontier handed it is 100000th block earlier this week. Listed below are some fascinating stats from these first blocks.
The primary 50 block instances (in seconds):
Proper after genesis, it took 29 seconds for the second block to look, then 31 and 29 seconds for the subsequent couple of blocks. Not too stunning because the miners scrambled with their setups as the ultimate genesis block turned recognized.
After these first blocks, we see the block time drop considerably on the onslaught of bigger miners, flooring at 1 second that’s the restrict enforced by the consensus protocol.
Let’s now take a look at the common block time (each 2 hundredth block from genesis to dam 10000):
We will see the hashing energy actually attacking the community after the primary few hundred blocks, with block instances at 1-2 seconds as the problem adjustment algorithm is catching up. This algorithm both will increase or decreases the problem by diff/2048 every block, relying on the block time.
After a couple of thousand blocks, we see the problem going up sufficient for block instances to get into the 4-5 second vary. After 9k blocks, we’re beginning to strategy the goal time of 15 seconds.
Greatest miners in first 100k blocks (tackle, blocks, %) :
0xef247e639d49461d25f57e9362cade3120910ce0 851 0.81% 0x790b8a3ce86e707ed0ed32bf89b3269692a23cc1 914 0.87% 0x0037ce3d4b7f8729c8607d8d0248252be68202c0 949 0.90% 0xbb12b5a9b85d4ab8cde6056e9c1b2a4a337d2261 1102 1.04% 0x580992b51e3925e23280efb93d3047c82f17e038 1129 1.07% 0xf2d2aff1320476cb8c6b607199d23175cc595693 1141 1.08% 0x47ff6576639c2e94762ea5443978d7681c0e78dc 1159 1.10% 0x1b7047b4338acf65be94c1a3e8c5c9338ad7d67c 1335 1.26% 0xeb1325c8d9d3ea8d74ac11f4b00f1b2367686319 1446 1.37% 0xbcb2e3693d246e1fc00348754334badeb88b2a11 1537 1.45% 0xa50ec0d39fa913e62f1bae7074e6f36caa71855b 1692 1.60% 0xf8e0ca3ed80bd541b94bedcf259e8cf2141a9523 2437 2.31% 0x9746c7e1ef2bd21ff3997fa467593a89cb852bd0 3586 3.39% 0x88d74a59454f6cf3b51ef6b9136afb6b9d405a88 4292 4.06% 0xbb7b8287f3f0a933474a79eae42cbca977791171 8889 8.41% 0xf927a40c8b7f6e07c5af7fa2155b4864a4112b13 9151 8.66% 0xe6a7a1d47ff21b6321162aea7c6cb457d5476bca 11912 11.28%
Whereas one can by no means know for positive whether or not a single miner makes use of a number of coinbase addresses, assuming they use a single one, we’ve got a fairly even distribution of hash energy over the primary 100k blocks. 0xe6a7a1d47ff21b6321162aea7c6cb457d5476bca with 11% of hashing energy is ethpool, the primary mining pool for Ethereum. Subsequent we’ve got two giant miners with round 8%. After these three the distribution is kind of even, with most miners having lower than 1% of whole hashing energy.
Nevertheless, issues develop quickly within the Ethereum world and if we take a look at the final 15k blocks we see:
0x580992b51e3925e23280efb93d3047c82f17e038 327 2.2% 0xbb7b8287f3f0a933474a79eae42cbca977791171 496 3.3% 0xf927a40c8b7f6e07c5af7fa2155b4864a4112b13 612 4.1% 0x790b8a3ce86e707ed0ed32bf89b3269692a23cc1 674 4.5% 0xe6a7a1d47ff21b6321162aea7c6cb457d5476bca 5775 38.5%
Right here it is clear ethpool is at the moment having nearly 40% of the hashing energy, and the 2nd and third largest miners are all the way down to 4%
Blocks in a row
One other fascinating stat is to have a look at steady units of blocks from the identical miner. This may give some perception into how hashing energy and latency is coming into play for bigger miners.
Early after launch, most blocks in a row we noticed was 6, for instance blocks 1578, 1579, 1580, 1581, 1582 and 1583 mined by 0x9dfc0377058b7b9eb277421769b56df1395705f0.
0xbb7b8287f3f0a933474a79eae42cbca977791171 additionally mined 6 blocks a couple of instances, for instance blocks 656, 657, 658, 659, 660 and 661.
This miner additionally mined 5, 4, 3 and a pair of blocks in a row on plenty of events, not too stunning with 21% of the entire hashing energy on the time.
This occurred very early after launch when problem was quickly rising and plenty of miners had not but joined the community. As hashing energy evened out after block 5000 we didn’t see greater than 4 blocks in a row for a while.
Nevertheless, lately probably the most blocks in a row is 10, for instance blocks 103049, 103050, 103051, 103052, 103053, 103054, 103055, 103056, 103057, 103058 by ethpool. Excluding ethpool, no miner has had greater than 6 blocks in a row.
Keep tuned for extra statistics from the Frontier community as we observe it over the subsequent months!
Gustav Simonsson is a developer within the Ethereum Safety and Go groups.
