...
lack of transactions in a block does not make it invalid, the miner may choose not to add any transactions (except the Coinbase transaction which states where the rewards should go to), however, most often than not, this isn't done with the intention of not wanting to add transactions, miners will start working on the next block right after a block is found, it takes a bit of time to deal with their mempool as they need to download the previous block's transaction list and remove all those transactions that were included in that block (failing to do so the block will be invalid).
So while downloading and working on the transactions, miners will start trying, if someone manages to hit a block before including any transactions, they will not hesitate to propagate the block, and that's how you see empty blocks.
...
It would be important to give some context to this statement rather than give them an excuse for not confirming transactions in a block before sending out work.
The time gained is like 10-50ms at most.
None of the large pools do block changes in 0ms - obviously, and pools like this and others can easily download and do a full block change with all the block's transactions fully verified in 10-50ms, often at the lower end of that range.
It hardly sounds like an excuse in mikeywith's comment, its merely a simple explanation for the not so "guru" minded people like yourself.
so i would take it that pools like yours? being almost 262 days since you hit a block and 8.5PH of shared mining
would be on the lower end of that range?
please explain?
KanoPool: 8.53PHs/8.51PHs
Shares: 26,480,887,347,784 (99.51%)
Invalids: 2.1M (0.13%) · 21.6G (0.08%)
Last Block
Pool: 262d 15h 38m (PPLNS 706643)
Network: 5m 17s (745043)
Users: 93
Workers: 225