4454ba8c816f1a1d40970c9def42b57ee4c36c5731aea993caf4678c7d7b9f99
Summary
Location |
167,705 confirmations
|
---|
Inputs |
6
72,600,624 sats
|
---|---|
Outputs |
1
72,446,766 sats
|
Fee | 153,858 sats |
---|---|
Size | 586.50 vbytes |
Fee Rate | 262.33 sats/vbyte |
Features | Segwit RBF |
---|
Transaction Data
1
- Basic Transaction
Inputs (6)
Raw Transaction
Bytes | 1,071 | 425 + 646 |
---|---|---|
Weight Units | 2,346 | 425 x 4 + 646 x 1 |
Virtual Bytes | 586.50 | 425 x 1 + 646 x 0.25 |
01000000000106a9a55a97a9f4ac0614a455e30e659d2605129791310e34e1f62ebc118955aaca4900000017160014b1bde00319d96cc1ebe93fd73cd17b6a677a56fcffffffff91926c18a2a2a81542d21be4bc6adc410d46b960ac5197fad78bfb8eb1f7d2602000000017160014b43206e990ace7a3b9142c12361f402558cacd6dffffffff9a6195308fd7186a35ad143f1a14507cca305d702dc1a4703a2eb67f276158712f0000001716001461bf033bf81b10428e346e00d728f46f22df5967ffffffff1cc8582b0381239f93da14c616288c9e2deb68b2197bfc844eb4f7578b8d6d9a2800000017160014dd90978e43c2d5df50922e1b7d00e1a0972a18ebffffffff930e50e0467fd43ae2954c083cc8bb0f16ee003af268b40a912024e654f883d91f000000171600145166b238d149e7cb086ea70e9092755320dcd234fffffffff52c97faf8c6292f081f1e40c43b6a17272d49ae8f4024d8e71946a267ead79d0a00000017160014f72899e8e4265ee0d6f9111cb65a607061c3750affffffff012e73510400000000160014d677c4cd066e6bb9852e2bdebb92787f4ca3bd0102473044022007cf27a0a920e038a027e8144081ddfb5ed2380b20467332656fa0684c3299b902203d7dab5679e3d0a85d461a8677f1e1bbf93728fd4e6d9adf366083bee5e762f10121028fbd6858a57b38d43e8e587536aaef7f54061054cf9bd86fd45f66d98b1b3aa10247304402205609a16ba7d85694fc6299c113c07529bf5cdf5ff88f8d57720b45d708de23cd02201f5c2aa6325c6454fa7faece8c90a3bb10152e6bc26672d23cceeed34969624c0121032001f57e7c45022de67dfd59059336c6f31ece8b4b59ae7a51ad5e0690767e0f02483045022100a2b3fd10082c0486d4fb21e6ae9471ed43299626aea41304c0929ecd5e3714a3022004c0a3059ef4752fb8e5e152b30a60c2832ae1ff4a0acede5e69d892ece3d9700121023274492f5ef6bb788e074d123f36b8a0af98cd7c97be4f7db3f14bf549fb5b9e02473044022023ecd0a693d7ed5615a3f99a5c481a077725a9edcf0f21b614e4523cb95ea35b022039cdfd74aedd7e416add8f1fe91277fdbe9754bf4a239f8843f324fa8fff5a69012103fc83935a7129bc1319310b3a3589d7bcd8e85bdc222370f7bb1fa52f794fb4fa024830450221008e75eae45e3af2f693e50873e2f3b0de280a5e2e47fcd2122208f30d04e430a1022077f36437289fad7116d97cd26bbcadd2794cbe7e3069c2135348eabc8bcc562a012102379c98aaeda7351f0d88f7a03d8ccd69bb3061ed816f43b094ea11813a52cbeb024730440220230a2a32ae12c7f773dbbd0cf631cb3d0eaf26939ef1474b28f5c50d8009598702204d9102f3c6106ada20f90f551c40f98c1054d7a1e14c2e1a8ca2fcdff0ed9dc80121026fffb568c92aa8579b411348051f25b9a9a8db881b69c4ac5a3e63744299073700000000
wTXID
3521412b3129c8c5f6b2637e01299779ed949b5b9d4857ec90c856f34519a455
The wTXID is the hash of the entire transaction data (including witness data).