Next scheduled rescrape ... never
Version 1
Last scraped
Scraped on 28/05/2025, 16:59:09 UTC
Here’s an overview how large transactions of each type are: 


Type|Input  vbyte|Output vbyte|transaction vbyte
Taproot|57,5|43|111
Native SegWit|68|31|109.5
Nested SegWit|93|32|134
Nested SegWit|140|34|192

For each input, we will save additional transaction fees.
You mean legacy address where I bold.

Most wallets as of today are using native segwit as the default which makes native segwit transaction make up more than 95% of the total bitcoin transaction. Those exchanges are the ones that isare still making use of legacy addressaddresses the most.
Original archived Re: My 2 big reasons why we should use SegWit addresses instead of Legacy addresses
Scraped on 28/05/2025, 16:54:16 UTC
Here’s an overview how large transactions of each type are: 


Type|Input  vbyte|Output vbyte|transaction vbyte
Taproot|57,5|43|111
Native SegWit|68|31|109.5
Nested SegWit|93|32|134
Nested SegWit|140|34|192

For each input, we will save additional transaction fees.
You mean legacy address where I bold.

Most wallets as of today are using native segwit as the default which makes native segwit transaction make up more than 95% of the total bitcoin transaction. Those exchanges are the ones that is still making use of legacy address the most.