Transaction

16a4b76f8e31e945e8ee3c6161fd60cf48dc2fb5ca0a60ea4c91b05edfa564b5
Timestamp (utc)
2024-03-22 15:44:49
Fee Paid
0.00000015 BSV
(
0.00485986 BSV
-
0.00485971 BSV
)
Fee Rate
10.29 sat/KB
Version
1
Confirmations
94,494
Size Stats
1,457 B

2 Outputs

Total Output:
0.00485971 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM´<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=461.msg5745#msg5745">Quote from: lachesis on July 25, 2010, 08:30:16 PM</a></div><div class="quote"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=461.msg5741#msg5741">Quote from: gazoakley on July 25, 2010, 08:08:02 PM</a></div><div class="quote">Whilst putting some security in is a good idea, it appears the JSON-RPC PHP doesn't support basic HTTP authentication right now. It'd have to be hacked in. Is anyone else using similar libraries going to encounter the same problem?<br/><br/>Also, whilst we're on the subject is bitcoind only binding to the loopback interface?<br/></div>The PHP library I'm using definitely supports HTTP Basic authentication. You just have to craft the URL right:<br/><a href="http://username:password@localhost:8332/">http://username:password@localhost:8332/</a><br/></div><br/>Of course, you can specify the username and password as part of the URL <img alt="Cheesy" border="0" src="/static/img/emoticons/cheesy.gif"/>. Think a BC or two is deserved for that one&nbsp;<img alt="Smiley" border="0" src="/static/img/emoticons/smiley.gif"/> - sent.</div> text/html
    https://whatsonchain.com/tx/16a4b76f8e31e945e8ee3c6161fd60cf48dc2fb5ca0a60ea4c91b05edfa564b5