Transaction

6176a593fdbb01a5aba7defe1ea089c8b84c72ff965b3f223075d683dbee2f90
Timestamp (utc)
2024-03-23 01:15:32
Fee Paid
0.00000011 BSV
(
0.03766041 BSV
-
0.03766030 BSV
)
Fee Rate
10.3 sat/KB
Version
1
Confirmations
104,437
Size Stats
1,067 B

2 Outputs

Total Output:
0.03766030 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM.<div class="post">It is normal for some blocks not to be accepted.&nbsp; One connection is enough, the others are just redundant.&nbsp; The client will make 8 outbound connections but will accept all inbound connections (on port 8333).<br/><br/>The blocks are generated in sequence so if two nodes happen to generate at almost the same time there will be a collision and one or the other will win.&nbsp; If the current block count is 5000 and your node finds a suitable block 5001, but meanwhile some other node already created a 5001 and your node just didn't know because it's on a laggy connection possibly, your block won't be valid and you have to start searching for 5002.&nbsp; I think this is explained in the pdfs, I'm not sure.<br/><br/>Are you seeing a lot of these happen or was it just one?<br/></div> text/html
    https://whatsonchain.com/tx/6176a593fdbb01a5aba7defe1ea089c8b84c72ff965b3f223075d683dbee2f90