Transaction

fe8e94de77c5ca2a72a77f33fdbce08b711941cf35374719057ebb45f55e3c3e
Timestamp (utc)
2024-03-30 10:50:20
Fee Paid
0.00000012 BSV
(
0.00179102 BSV
-
0.00179090 BSV
)
Fee Rate
10.16 sat/KB
Version
1
Confirmations
95,577
Size Stats
1,180 B

2 Outputs

Total Output:
0.00179090 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMŸ<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=898.msg11074#msg11074">Quote from: satoshi on August 24, 2010, 11:51:12 PM</a></div><div class="quote">If you're so paranoid that you're getting hysterical over this, then surely you're paranoid enough that if a warning message displays on the status bar, you'll check the website and forum.<br/><br/>I think if another bug like the overflow bug occurs, it's important that automated websites stop trading until their admins can check out what's going on and decide what to do. &nbsp;If you decide it's a false alarm and want to take your chances, you can use the "-disablesafemode" switch.<br/><br/></div><br/>So what kind of warning do admins get from bitcoind? Is there something we can grep from debug.log? Or will rpc calls raise some specific error? Is there a way to locally force this to happen, for unittesting services?</div> text/html
    https://whatsonchain.com/tx/fe8e94de77c5ca2a72a77f33fdbce08b711941cf35374719057ebb45f55e3c3e