Transaction

5ccd4ddf865c9682ebcea351c19b469cb111402ca77a253ebdbbe823a6b82fb6
Timestamp (utc)
2024-04-03 00:13:54
Fee Paid
0.00000015 BSV
(
0.01067548 BSV
-
0.01067533 BSV
)
Fee Rate
10.6 sat/KB
Version
1
Confirmations
95,550
Size Stats
1,414 B

2 Outputs

Total Output:
0.01067533 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMŠ<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=632.msg6636#msg6636">Quote from: martin on July 30, 2010, 11:37:59 AM</a></div><div class="quote">The encoded protocol buffer is just 55 bytes, wheras the bitcoin version is 85 0x00 sets (each one representing 2 bytes each I assume). This means that my badly designed protocol buffer is over half the size of the hand built layout!<br/></div>The "0x00" groups each represent one byte. The length of the standard version packet is 87 bytes plus 20 for the header. The header could be massively optimized as well:<br/><div class="codeheader">Code:</div><div class="code">message start "magic bytes" - 0xF9 0xBE 0xB4 0xD9<br/>command - name of command, 0 padded to 12 bytes "version\0\0\0\0\0"<br/>size - 4 byte int<br/>checksum (absent for messages without data and version messages) - 4 bytes<br/></div>Obviously using proto buffers here, while absolutely a breaking change, would save a fair bit of space, especially because the "I've created a transaction" packet has the name "tx" meaning that there's at least 10 bytes of overhead in every one of those packets.</div> text/html
    https://whatsonchain.com/tx/5ccd4ddf865c9682ebcea351c19b469cb111402ca77a253ebdbbe823a6b82fb6