Transaction

097b3a36a8cb5effa67e7750ba1a2c52a11e7dd14c8e2254832cc9d4b0dfbae0
Timestamp (utc)
2024-03-22 14:22:06
Fee Paid
0.00000014 BSV
(
0.00590629 BSV
-
0.00590615 BSV
)
Fee Rate
10.37 sat/KB
Version
1
Confirmations
94,243
Size Stats
1,350 B

2 Outputs

Total Output:
0.00590615 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMI<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1291.msg14263#msg14263">Quote from: Marko on September 27, 2010, 04:50:25 PM</a></div><div class="quote">I read the wiki and it says the interface only accepts requests from 127.0.0.1. Is this still the case? Is there a setting to override this?<br/></div><br/>This is still the case and I don't believe there is a setting to override it. It's hardcoded in the source. Instead of writing a 'proxy' app you can use SSH to tunnel. For example, if your bitcoin instance is running on 'example.com' and that machine is running an ssh server, you can tunnel to it from another machine with:<br/><br/>ssh -N example.com -L&nbsp; 9481:localhost:9481<br/><br/>Now you can use the RPC interface on your local machine to port 9481 and it will be tunnelled over an encrypted SSH session to the machine running the bitcoin RPC server.<br/><br/>You want to encrypt the connection because the JSON-RPC password is sent in clear text (it's actually base 64 encoded but basically it's the equivalent of clear text).</div> text/html
    https://whatsonchain.com/tx/097b3a36a8cb5effa67e7750ba1a2c52a11e7dd14c8e2254832cc9d4b0dfbae0