b609ef12161521e4118e4e4044643c8249ff4ce99743442a668e34e06f1a3074
Summary
| Location |
324 confirmations
|
|---|
| Inputs |
6
2,062,978 sats
|
|---|---|
| Outputs |
1
2,058,778 sats
|
| Fee | 4,200 sats |
|---|---|
| Size | 589.75 vbytes |
| Fee Rate | 7.12 sats/vbyte |
| Features | Segwit RBF |
|---|
Transaction Data
2
- Relative Locktime Available
Inputs (6)
Raw Transaction
| Bytes | 1,075 | 428 + 647 |
|---|---|---|
| Weight Units | 2,359 | 428 x 4 + 647 x 1 |
| Virtual Bytes | 589.75 | 428 x 1 + 647 x 0.25 |
02000000000106745506b214b4891c585ae672011d95012646f8066872fb72f0d54a716d359dec1a00000017160014c55b814cf13d07bb551cca3fe20c8a685230af34ffffffff10618b90600f47ed801b89d71d3b1262dd714936d171963f546c61ef33fd90d89a00000017160014c55b814cf13d07bb551cca3fe20c8a685230af34ffffffffd60f1632913673aaaf52d92b89d3c4683c427d4e0c1134febf44a07725948f6f5a00000017160014c55b814cf13d07bb551cca3fe20c8a685230af34ffffffffb02d3b90bc32c11f0dfa59698846d7944109792ec1332adfa7bf33b0bf7d7d8d2a00000017160014c55b814cf13d07bb551cca3fe20c8a685230af34ffffffff53a2904d9d65e90602ba649b37034aed6918a9ab6bfe5e52ce2ae69474ecde51ad00000017160014c55b814cf13d07bb551cca3fe20c8a685230af34ffffffff17f13dc03ddcecc21db4f59f6ae6b5cb0e90152fadb0eb7551cd77aa9893ffce4600000017160014c55b814cf13d07bb551cca3fe20c8a685230af34ffffffff011a6a1f00000000001976a91460b55247e198c6a2729beada2959e206dde89b1d88ac024730440220011bdb04b5a641e6be6a695862a7c18e7905a2a46c692ac0941a54a3cee5ce6002206ad525e17b4b43bab67adfbd8b3a5cf746861a424a0ec74edda3f9489dbd20640121023bb01f2f2b513ab97b58b73d7adffcd679f2e45b9e7ae130af6947945cb438b90248304502210099ba486034a1ca7c8d2f510b17e3863e8534fe90cefe6a7a06122dcb657ebf0f02204f2c81c9eb544e5b33e693593f2a40232e00059eb7c4bd36877bc44b5f19f5f20121023bb01f2f2b513ab97b58b73d7adffcd679f2e45b9e7ae130af6947945cb438b90247304402202462b71a9448910f8f9d12d72de5b569b5842f2555caa3c04c726a47af44d35e02201bf4e1a9c67bf730631db9153ea9caefe2d0f87d4d23f8c9d4b34d468aaaeb660121023bb01f2f2b513ab97b58b73d7adffcd679f2e45b9e7ae130af6947945cb438b902483045022100c03789816571bdc22b488444b06dfeabfd5e8953a91ae1144e2307da783346b10220498190b870a338aec6abae906f3c9027f73d758ee63e9da5a62cad45832218dc0121023bb01f2f2b513ab97b58b73d7adffcd679f2e45b9e7ae130af6947945cb438b902473044022058878af9b23ec3d1747309d5887f9b4d976dcc7695a261c6f107a208d9c60e7702203614fde4c0c516bda519e971892ea19dc78570e4fef3b21db514ec6ef5de013a0121023bb01f2f2b513ab97b58b73d7adffcd679f2e45b9e7ae130af6947945cb438b902483045022100870a14ddef09eb9cb4cd23c69ac53b49ceb7b1d299853759121b465779082ded02205d61b4fd6adc85cf2e286c09dd3963bd27aa4d23b024e5e997097ef8302481330121023bb01f2f2b513ab97b58b73d7adffcd679f2e45b9e7ae130af6947945cb438b900000000wTXID
b1a21f861eedf40681d4d771c157c33ff10f54f56e8f8b9ffeaad9067c31dd3e
The wTXID is the hash of the entire transaction data (including witness data).
