solominer icon indicating copy to clipboard operation
solominer copied to clipboard

Hashing old Block after Restart

Open GitHappens2Me opened this issue 1 year ago • 0 comments

On some occasions the log shows that an old block is being mined.

This is part of the log: As you can see, the script acknoledges that Block 792575 was mined and restarts. After the restart it continues to show calculated hashes for Block 792575.

2023-06-02 19:01:04,709 [*] New hash: 000000cf7cae0e2ca0fdc982e77a2d177cb3ed3bbedcc8b304d275d509f6b4cb for block 792575
2023-06-02 19:03:10,300 [*] New hash: 00000a7c39d8d775590364cc181289f09c08fc41a71c57ad561f78fae65332a7 for block 792575
2023-06-02 19:03:35,173 [*] New block 6a5fca7ac0452c1234c241396c93663fccec59e00000ffc70000000000000000 detected on network
2023-06-02 19:03:35,173 [*] Best difficulty will trying to solve block 792575 was 0.004819578340809793
2023-06-02 19:03:35,173 [*] Bitcoin Miner restarted
2023-06-02 19:03:45,512 [*] Working to solve block with height 792575
2023-06-02 19:05:14,620 [*] New hash: 00000c6af823df238fdbc17dad62415acd49e7ec492b99eb4322201d9597c865 for block 792575
2023-06-02 19:06:30,913 [*] New hash: 00000a6f2b0ae7e9b3fa05bcb7d0697f18fee1592ef3ec1c70e8f2f09bb79d2b for block 792575

I did not find any indication on if this is only a logging error or if the block is really being mined. Any Idea on what could cause this behaviour?

GitHappens2Me avatar Jun 02 '23 17:06 GitHappens2Me