No Slush, you are WRONG! See my picture, where's yours if you really got it? Yeah...didn't think so.
Firstly, I don't understand why you're so aggressive, we're just talking about block numbers. I don't say you're lying, I just said that two blocks are mine and that there is known problem with bitcoind
.
Next, I don't see any block number in picture you've posted. How you can be so sure that this payout was from block #114974?
It's important to track this correctly, and you've openly admitted (and it's still visible) that your site seems to have a problem tracking blocks.
LOL, you're funny. I like your arrogance, especially when I'm ABSOLUTELY sure that I'm right. There is an evidence:
a) Block 114974 has hash
000000000000da97d2ba7ddb5d3c9b48980b92bb12f3926bb0382615853fbaca. This hash was posted by pool user 'jar', I have this hash in my log. I cannot have this hash in _my_ log if one of my miner didn't find it.
b) As you see in block explorer, the bitcoins from generated blocks were transferred to address 1PJnjo4n2Rt5jWTUrCRr4inK2XmFPXqFC7, which is my pool's central wallet. You can check it for example
here, it's my pool payout using this address.
c) Block 114974 has no transactions inside, thats because at this time my pool didn't accepted free one because of tx spam problem (pool started accepting fee tx few hours later).
Our site tracks blocks just fine with no problems. Why don't you fix your own site before you try and criticize other people's pool.
The bug on my side is well documented and I'm sure THIS is not the case. Please accept that your pool has even bigger problems with tracking the blocks
.
By the way - because of your tone, which was absolutely unnecessary, I want your apologize.