I assume you are still going to pay me for that orphaned block. I threw up a 50,869 share.
Just kidding on the paying me.
I know that you are kidding
that shit happens from time to times unfortunately. But it was close to be valid just four seconds late
2015-09-10 00:15:31 [2015-09-10 00:15:31+00] UpdateTip: new best=a69a89feb817389182b5c5abcfc6d8f733ba2898f0ea035cc2ca171270af4361 height=848727 log2_work=65.324466 tx=6645255 date=2015-09-10 00:15:11 progress=0.999999 cache=175
2015-09-10 00:15:31 CreateNewBlock(): total size 1000
I do have external hook to LTCd to notify pool about block changes. In the same moment (almost we are talking about milliseconds) your miner receives that info also. But that shit happens ...
[2015-09-10 03:15:31.647] Block hash changed to a69a89feb817389182b5c5abcfc6d8f733ba2898f0ea035cc2ca171270af4361
[2015-09-10 03:15:35.406] Possible LTC block solve diff 3333773520.168740 < 2779361203.741573(2807435559.334922)!
[2015-09-10 03:15:35.406] Submitting block data!
[2015-09-10 03:15:35.411] SUBMIT BLOCK RETURNED: inconclusive
[2015-09-10 03:15:35.412] Submitted, but rejected block 848727
As you see I am sure that you miner was aware that this block was stale but submitted winning share just in case
Same apples for pool - it checks your job hash and if share difficulty is good enough to solve a block it gets submitted to LTCd just in case:)
Later on pool checks if your share is stale or not and sends you reject:D
You know we have a saying: Hope dies last