Transaction

a75672b098e2bb94de5c679e55c07ce399a5a8dfc62ae61aeda356d09974c30b
Timestamp (utc)
2024-03-24 08:15:57
Fee Paid
0.00000009 BSV
(
0.01635163 BSV
-
0.01635154 BSV
)
Fee Rate
10.32 sat/KB
Version
1
Confirmations
102,801
Size Stats
872 B

2 Outputs

Total Output:
0.01635154 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/a75672b098e2bb94de5c679e55c07ce399a5a8dfc62ae61aeda356d09974c30b