Transaction

359434ca3e3f68bc026fed44b85fcbc229e7a5bb5de3fd454dba9cda9bd9b6ec
Timestamp (utc)
2024-03-22 09:20:47
Fee Paid
0.00000013 BSV
(
0.00923218 BSV
-
0.00923205 BSV
)
Fee Rate
10.33 sat/KB
Version
1
Confirmations
93,902
Size Stats
1,258 B

2 Outputs

Total Output:
0.00923205 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMî<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=632.msg6565#msg6565">Quote from: lachesis on July 30, 2010, 01:04:06 AM</a></div><div class="quote"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=632.msg6547#msg6547">Quote from: martin on July 29, 2010, 11:29:31 PM</a></div><div class="quote">Some people have been suggesting that protocol buffers might be larger than the custom written packet layout. I suspect that actually it would be *smaller* due to some of the clever encoding used in protocol buffers. <br/></div>I agree that it could be smaller; not necessarily because of clever encoding, but because it would allow us to drop reserved bytes and the like.<br/></div><br/>Not only does it allow it to drop reserved fields, but it uses ZigZag encoding and some other tricks to keep integers and the like as absolutely small as possible.&nbsp; So yea, it uses clever encoding. =P&nbsp; It's also blazingly fast to process!</div> text/html
    https://whatsonchain.com/tx/359434ca3e3f68bc026fed44b85fcbc229e7a5bb5de3fd454dba9cda9bd9b6ec