I've already checked everything twice without noticing any problems but I'm going invest some more time today.

Yep. Now would be the best time Jim.

Nope we weren't mining on the wrong chain for long. That's exactly what confused the heck out of me. The block in question was not updated even while monerod claimed to be fully in sync. I saw our orphan as legit, non-orphaned block on the chain. Only when I forced a restart of the daemon, I was able to see both the "real" block and our orphan.

Block 1595437 is fine as well. :)

There was a DNS issue that has been fixed now. Sorry for the confusion guys.

Not at all. The whole situation was quite embarassing for me since I struggled to find out what the heck was going on with that block.

The DGB-Scrypt pool is now open for mining: https://coinfoundry.org/pool/dgb2

DGB-Scrypt is coming tommorow.

Block is 1594145 is not an orphan by the way. Already checked it.

There's of course a non-orphaned block 1589929 shown on chainradar. Unfortunately the non-orphaned version has a hash of bb4e624526aa290b3149fa241ae8a2fffd4ae176f2afcfcc239f2b695a29fbba. The one mined on our pool has a different one which made it orphan in the first place. This is block 1589929 how its been submitted by the miner that found the orphan:

miningcore=# select * from blocks where poolid = 'xmr1' and blockheight = 1589929;

  id   | poolid | blockheight | networkdifficulty |  status  | type | confirmationprogress |      effort      |                   transactionconfirmationdata                    |                                             miner                                              |     reward     | source  |                               hash                               |          created
-------+--------+-------------+-------------------+----------+------+----------------------+------------------+------------------------------------------------------------------+-------------------------------------------------------------------------------------------------+----------------+---------+------------------------------------------------------------------+----------------------------

 12006 | xmr1   |     1589929 |       52774831374 | orphaned |      |                    1 | 0.17212013521421 | 5294849d7c578227966a2fb5cb6a4155038464c57c5810d1820b27df826b2487 | 47qeoHL28ywM9e2xHJosxSJ8trM4v3GWKCTUWMYwe1eE46o5NR3UPvWN11PLNxGnssdCXUHP6vcsBfgure5aAm3hKLh6JLt | 0.000000000000 | us-east | 5294849d7c578227966a2fb5cb6a4155038464c57c5810d1820b27df826b2487 | 2018-06-08 11:29:36.490749
(1 row)

Note the blockhash in green. Querying monerod for a block with this hash yields:

curl --data-binary '{"jsonrpc": "2.0", "id":"1", "method": "getblockheaderbyhash", "params": { "hash": "5294849d7c578227966a2fb5cb6a4155038464c57c5810d1820b27df826b2487" } }' -H 'content-type: application/json' -X POST http://127.0.0.1:18081/json_rpc
{
  "id": "1",
  "jsonrpc": "2.0",
  "result": {
    "block_header": {
      "block_size": 104,
      "depth": 3365,
      "difficulty": 52774831374,
      "hash": "5294849d7c578227966a2fb5cb6a4155038464c57c5810d1820b27df826b2487",
      "height": 1589929,
      "major_version": 7,
      "minor_version": 7,
      "nonce": 2865252,
      "num_txes": 21,
      "orphan_status": true,
      "prev_hash": "b3b72c9affb658ac673eab4eec145a2fa0f7991a4937a27ad8fda87fdccc09d0",
      "reward": 4676461370602,
      "timestamp": 1528392962
    },
    "status": "OK",
    "untrusted": false
  }
}

I have not a never will cheat our miners of their rewards.