Transaction

c6d1e5ee88d37d6e02840cee9331ebaeb770611fcccb03a50bfdb5ab6fdc78ea
Timestamp (utc)
2024-03-22 12:51:13
Fee Paid
0.00000011 BSV
(
0.00682091 BSV
-
0.00682080 BSV
)
Fee Rate
10.26 sat/KB
Version
1
Confirmations
94,397
Size Stats
1,072 B

2 Outputs

Total Output:
0.00682080 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM3<div class="post">Yeah, my opinion on this is that the GUI should be separated from the underlying code. BUT... there's no need to throw the baby out with the bathwater and I firmly believe that the current wxWidgets interface should be maintained until such a time as something superior comes along.<br/><br/>My personal feeling is that whilst separate daemon/GUI binaries can work, it also tends to be messy, I'd be far more in favour of having the core code and then separate source that you compile with it according to your target OS, that way everything is still a single binary and can be integrated as idealistically as possible.<br/><br/>To put this in practice, imagine 3 SVN trunks; the first is BitCoin core, the other two are LINGUI and WINGUI - the latter two being dependant on code from the first.</div> text/html
    https://whatsonchain.com/tx/c6d1e5ee88d37d6e02840cee9331ebaeb770611fcccb03a50bfdb5ab6fdc78ea