different transactions at the same height in history (hafah response vs reference response)

See the example of account gtg, transaction number 2345678
Request:
{"id":9,"jsonrpc":"2.0","method":"account_history_api.get_account_history","params":{"account":"gtg","start":2345678,"limit":1}}
HAfAH Response:

{
  "jsonrpc": "2.0",
  "result": {
    "history": [
      [
        2345678,
        {
          "trx_id": "0000000000000000000000000000000000000000",
          "block": 50361159,
          "trx_in_block": 4294967295,
          "op_in_trx": 1,
          "virtual_op": true,
          "timestamp": "2021-01-12T00:58:00",
          "op": {
            "type": "producer_reward_operation",
            "value": {
              "producer": "gtg",
              "vesting_shares": {
                "amount": "493984540",
                "precision": 6,
                "nai": "@@000000037"
              }
            }
          },
          "operation_id": 0
        }
      ]
    ]
  },
  "id": 9
}

Reference (api.hive.blog) Response:

{
  "jsonrpc": "2.0",
  "result": {
    "history": [
      [
        2345678,
        {
          "trx_id": "0000000000000000000000000000000000000000",
          "block": 50361341,
          "trx_in_block": 4294967295,
          "op_in_trx": 0,
          "virtual_op": 1,
          "timestamp": "2021-01-12T01:07:09",
          "op": {
            "type": "producer_reward_operation",
            "value": {
              "producer": "gtg",
              "vesting_shares": {
                "amount": "493984248",
                "precision": 6,
                "nai": "@@000000037"
              }
            }
          },
          "operation_id": 0
        }
      ]
    ]
  },
  "id": 9
}

Those are different transactions, different blocks. Please note that in complex server environment (load balancer with underlying mix of Hived's RocksDB AH and HAfAH) one can get a history with duplicates or missing entries.