Transaction

dbb45eefa82156b4e4eff5f10497a14ea4b547f609db0c613e1bbef7aae15e5a
Timestamp (utc)
2024-03-29 22:19:07
Fee Paid
0.00000013 BSV
(
0.00282836 BSV
-
0.00282823 BSV
)
Fee Rate
10.13 sat/KB
Version
1
Confirmations
93,500
Size Stats
1,283 B

2 Outputs

Total Output:
0.00282823 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM<div class="post">Right now there isn't a port number setting to do that. &nbsp;It's a feature yet to be implemented. &nbsp;You can only set up your NAT to port-forward to one of the computers. &nbsp;(I said something earlier about NAT port translation, but that wouldn't work, other nodes wouldn't know to connect to that port)<br/><br/>If you want, as a small optimization, you could run the rest of your computers as:<br/>bitcoin -connect=&lt;the IP of the first computer&gt;<br/><br/>so they get all their network communication from the first computer and don't all connect over the net individually for the same information. &nbsp;This saves bandwidth, although it doesn't use much bandwidth to begin with, so it wouldn't really matter unless you had tons of computers.<br/><br/>For redundancy in case the first computer goes down, you could have two that connect out and the rest connect to both of them. &nbsp;The first two are run normally, the rest are run like:<br/>bitcoin -connect=&lt;IP1&gt; -connect=&lt;IP2&gt;</div> text/html
    https://whatsonchain.com/tx/dbb45eefa82156b4e4eff5f10497a14ea4b547f609db0c613e1bbef7aae15e5a