Transaction

fcbee2fec022f4d99469849437e8d146a5e991d0e0660ff4ede3c3aec145b31a
Timestamp (utc)
2024-03-29 20:23:00
Fee Paid
0.00000015 BSV
(
0.00299062 BSV
-
0.00299047 BSV
)
Fee Rate
10.27 sat/KB
Version
1
Confirmations
93,127
Size Stats
1,460 B

2 Outputs

Total Output:
0.00299047 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM¸<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=753.msg8226#msg8226">Quote from: lfm on August 08, 2010, 10:32:32 AM</a></div><div class="quote">This seems to be a different problem. The blocks do not seem to be "stuck" on my systems. The getinfo shows them up to date<br/><br/>It seems the sha256 code is not getting built right for linux 64. Not sure if/how it could work on some and not on others.<br/><br/><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=753.msg8219#msg8219">Quote from: knightmb on August 08, 2010, 07:20:20 AM</a></div><div class="quote">There is one behavior that I've noticed.<br/><br/><b>Block sync stalling.</b><br/><br/>When the client (be it Windows or Linux) has been running for a few days, *sometimes* they get stuck in block limbo. What happens is your client keeps trying to solve the current block and loses track of the entire block system. So as time goes by, other blocks are solved and your PC is still stuck on the same block.<br/><br/>...<br/><br/></div></div>I'm starting to wonder if the two are connected now since the hashing seems to get stuck, maybe that's why it gets stuck on a block.</div> text/html
    https://whatsonchain.com/tx/fcbee2fec022f4d99469849437e8d146a5e991d0e0660ff4ede3c3aec145b31a