Quote from: kano on January 18, 2016, 10:59:22 PM

Quote from: stonebone on January 18, 2016, 10:52:46 PM

Quote from: -ck on January 18, 2016, 10:49:15 PM

Quote from: Xunknown on January 18, 2016, 10:38:41 PM

Nice green block. Pretty empty thou...

Was found based on work only seconds after the previous block so there weren't many transactions around but the highest priority transactions pending still got included. This would have been a completely empty block if found by numerous other pools.

I like

That's exactly how it should work.

Yeah it was only 6.225 seconds after the previous block:

Code:

[2016-01-19 09:31:08.876] Block hash changed to 0000000000000000063a313addbe94086022924139e7c2be7ee1458a7b6629d2
[2016-01-19 09:31:15.101] Possible block solve diff 136869014868.750259 !
[2016-01-19 09:31:15.172] BLOCK ACCEPTED!
[2016-01-19 09:31:15.184] Block hash changed to 000000000000000008087f29ce6277f0982e33b56aaf15534793005a36674692

Living proof that it's possible to include TX's when finding blocks within seconds of each other with a properly coded pool. Miners - don't let any other pool try & tell you otherwise or fob you off with excuses.

Congrats & well done Kano & ck!