99f4e4345fd3947d4288e0a9ba052b1ca59119e70cb9f8075bb4a3f82010c8cb
Summary
Location |
609,424 confirmations
|
---|
Inputs |
6
25,027,125,652 sats
|
---|---|
Outputs |
2
25,027,025,654 sats
|
Fee | 100,000 sats |
---|---|
Size | 1,158.00 vbytes |
Fee Rate | 86.36 sats/vbyte |
Features | Segwit RBF |
---|
Transaction Data
1
- Basic Transaction
Inputs (6)
Raw Transaction
Bytes | 1,158 | 1158 + 0 |
---|---|---|
Weight Units | 4,632 | 1158 x 4 + 0 x 1 |
Virtual Bytes | 1,158.00 | 1158 x 1 + 0 x 0.25 |
01000000064e08ba3b1f1c05fd2af495ce9741638350296dae3557190705dac976f0e137f9000000008b48304502206f80b7edb7b9a33f20f5c8d8f8992520fbd3f6fd20a5e234edd805c869508b66022100be40c9a77097e6d3ed26e7028d4687766446387fb841f8e93ce01f8e52ac336c0141041749c0693f8e7c3c16742f36ac893aa3716f8430670760c3ee7af317b278d8e9e1a75a919e8548b9b238a4c4001991e0b31972a5e81fb3c4757f54ce455792b8ffffffff9dec20b932e48d9e3c4fcd63bfac0399dc36a9b3c621519667dd2e758014723c000000008a47304402200e5c3829fa3deb21dff704b7efa964a1d3bdfbbf016400e5775e7b5d0ac69bad02203f6ae9fb6549b2fbbee438d986c5d4f1d18245985ec5c518b92f6c92b811f6f50141041749c0693f8e7c3c16742f36ac893aa3716f8430670760c3ee7af317b278d8e9e1a75a919e8548b9b238a4c4001991e0b31972a5e81fb3c4757f54ce455792b8ffffffffd822d57016d79a94b63c83211b0fd81a046eb7cd3eacefb10630fc40b8c121e2010000008a4730440220745ef2077225f5c77574c9657e698bc995ded464e03fe7fa7f3a5a9d2b38e46a02204ff0d5541d3a171b8c5970c65d8e24e9afc93d6cd61e9e660ae4017c2356f3500141041749c0693f8e7c3c16742f36ac893aa3716f8430670760c3ee7af317b278d8e9e1a75a919e8548b9b238a4c4001991e0b31972a5e81fb3c4757f54ce455792b8ffffffff544ed60adc1c9efe8db2710ae9be047f8be5da2e69845d212100c466bb1f916e010000008c493046022100ae0b8aaace0b49e165c8e32c0a334005d0acd3cf625a23e2be45c1b2f06c4e23022100fa98d440e1418bea94742c5ed767ad85a10c4bc72988d9acc0895a0d207ee87c0141041749c0693f8e7c3c16742f36ac893aa3716f8430670760c3ee7af317b278d8e9e1a75a919e8548b9b238a4c4001991e0b31972a5e81fb3c4757f54ce455792b8ffffffffefd30e48641e1691072df904162e989a1d8c1dd9018fe2cd09700619fe1d2da8010000008b483045022100a3b22a3d9e02e7f2dd4cfcf5fccb0ba59d53b472a65db28255f964d2583fd08902204aeaab0689ebe3811461002e1529727bb732efbc3330e55c347af9fb1d413df70141041749c0693f8e7c3c16742f36ac893aa3716f8430670760c3ee7af317b278d8e9e1a75a919e8548b9b238a4c4001991e0b31972a5e81fb3c4757f54ce455792b8fffffffff49920494208f0f1e8717bd646b19c4fecb11049058e7be0ce82fcb55b67c3b9010000008c493046022100c84a74dc150559b9eb8a57a82e17b697c2db659793ebaffaf4bf020e6584dc6d022100cc2b48c0fca5642621240d321b0849012b4551691929c4ebb3d652b81ca8dd180141041749c0693f8e7c3c16742f36ac893aa3716f8430670760c3ee7af317b278d8e9e1a75a919e8548b9b238a4c4001991e0b31972a5e81fb3c4757f54ce455792b8ffffffff0200ba1dd2050000001976a9141a5898c82130b0655252d26b1199bbf98e4d411d88acf6609c01000000001976a914244114207f4451bed49bdb5c71de7afc10284b8088ac00000000
wTXID
99f4e4345fd3947d4288e0a9ba052b1ca59119e70cb9f8075bb4a3f82010c8cb
The wTXID is the hash of the entire transaction data (including witness data).