bbea8231857a0a8fc921d466021b4f4cb201deae5e5a521c09271d0bbc7af47f
Summary
Location |
272,268 confirmations
|
---|
Inputs |
6
534,581,268 sats
|
---|---|
Outputs |
2
534,419,751 sats
|
Fee | 161,517 sats |
---|---|
Size | 596.00 vbytes |
Feerate | 271.00 sats/vbyte |
Features | Segwit RBF |
---|
Transaction Data
1
- Basic Transaction
Inputs (6)
Raw Transaction
Bytes | 1,082 | 434 + 648 |
---|---|---|
Weight Units | 2,384 | 434 x 4 + 648 x 1 |
Virtual Bytes | 596.00 | 434 x 1 + 648 x 0.25 |
0100000000010623788027f9c7cf8daec86c8799179cab8ffd52ed4541a528400db71068ada92c000000001716001459168f0efb928af4deb81835971420c336f9dac7ffffffff4807862de559ac136fb743c9977e5fe43fcf04dfc3a0cd1cede7c1612ac32019000000001716001459168f0efb928af4deb81835971420c336f9dac7ffffffff08ab1475e5473c3547009f65d06569ed5b4f5d2ede1033217bb2ad1388096005000000001716001459168f0efb928af4deb81835971420c336f9dac7ffffffffd34380fb9a76477d48d4ba38effcfaf7bf692a097182b88fea3fea1fbde7a14b0000000000ffffffffed129fa69c52eb086d350bbf1d209b2b662df5a7d4c4a90edc0e884393b2c2c1000000001716001459168f0efb928af4deb81835971420c336f9dac7ffffffff733d6ac3f40cdec0caf00867e4b49d249cc6f0fa8f98dcd25499b4c0318db3ac050000001716001459168f0efb928af4deb81835971420c336f9dac7ffffffff026752280100000000160014b5da6528670590c4148cb288bca1a7e09b8eb5a4c046b21e0000000017a914c6ca9698ac914695740928a29cc2528d2ac8d9188702483045022100cb5e43df01d79426024eb9e97733e922effaa139765877f20c0a9c12b3b3892f02206711edce28d91f2d7188d4c536f23118586079f11e9ba4c31b098f288a25f467012102a85627587e5deaed4a90eb66aa0697855f0d5e392f16d2cdae581f89234c6bca02483045022100b91923d0722f62254384d21796c316380db7d0d1b5885d7925467cb212bf07ae022007cf419e5f887f57c19aecdfc33eb7998f492446d047c7575221dc120c333545012102a85627587e5deaed4a90eb66aa0697855f0d5e392f16d2cdae581f89234c6bca0247304402203e7bdf78487e8435ced8b30fe2d44197eb084abf376b9482462802cf1278536102203e6af7ec86179212d0daa3746e3acaad0fc52a710e1fbad68f0776e2f64065e6012102a85627587e5deaed4a90eb66aa0697855f0d5e392f16d2cdae581f89234c6bca024730440220772668cdc0227a4825457cec13e98bbf7db8333f5239a5bd87f81b4707e958c202206f52fa7a6475f160c5f4cc234fd851fbf170bbf324672efefa9e3a2f735f3c880121021b7f58b517c4a16cbe5dcec54c6d3252c51761922521664250fc33dec16d1ad8024830450221009bed2d21640b686ed7a49b00e1863722fda2e679d92e3bb3e8925d619831f24d02207a283a413fa454e58318a663fc9d2f033033496dfe66d302709cc2a6f0f1053f012102a85627587e5deaed4a90eb66aa0697855f0d5e392f16d2cdae581f89234c6bca02483045022100e41da1b72700ff2d400a70254145933370816eac82283960ba52d10c5de0b0990220340bf39b5a695c98c05ed48e097826d021777f7c17627e714a8b0ce4040056b0012102a85627587e5deaed4a90eb66aa0697855f0d5e392f16d2cdae581f89234c6bca00000000
wTXID
4419de46eaa343761f660136dffb7cd01a8bf444951691569e1926ee77b237e5
The wTXID is the hash of the entire transaction data (including witness data).