Transaction

b80c9e256eddbbe646fcd722fd4e8e9518f113eec210cc9753fee30c2649db2c
Timestamp (utc)
2024-03-22 09:36:30
Fee Paid
0.00000009 BSV
(
0.00910066 BSV
-
0.00910057 BSV
)
Fee Rate
10.32 sat/KB
Version
1
Confirmations
93,840
Size Stats
872 B

2 Outputs

Total Output:
0.00910057 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMk<div class="post">At the moment, it always assumes the incoming port is 8333, so it would tell other bitcoin nodes to connect to router:8333 even if you're redirecting from another port number.<br/><br/>I'm not in a big hurry to fix this because I can't think of any benefit to having more than one incoming connection port.&nbsp; If you're providing one incoming port, then you've done your bit to help the network.&nbsp; Having two incoming ports to the same person doesn't help redundancy.<br/><br/>If you have many computers, then using the -connect switch on most of them to connect locally makes more sense.</div> text/html
    https://whatsonchain.com/tx/b80c9e256eddbbe646fcd722fd4e8e9518f113eec210cc9753fee30c2649db2c