dec5a5d7ab0b4255c4785d8d7dbe85649bc4fec0b41f69318ac624e7310b53bf
Summary
Location |
12,271 confirmations
|
---|
Inputs |
6
579,705 sats
|
---|---|
Outputs |
9
578,165 sats
|
Fee | 1,540 sats |
---|---|
Size | 743.00 vbytes |
Feerate | 2.07 sats/vbyte |
Features | Segwit RBF |
---|
Transaction Data
2
- Relative Locktime Available
Inputs (6)
Raw Transaction
Bytes | 1,043 | 643 + 400 |
---|---|---|
Weight Units | 2,972 | 643 x 4 + 400 x 1 |
Virtual Bytes | 743.00 | 643 x 1 + 400 x 0.25 |
02000000000106b12684c416656d517b0d4cdd00aaed16f21c05565c245b7a00dfacfebc668a720300000000ffffffffb12684c416656d517b0d4cdd00aaed16f21c05565c245b7a00dfacfebc668a720400000000ffffffffa1f5c000c326e9621ce3b46650dfa11faea785031d11f8c00f15df7f4ef9c7270000000000ffffffffc2c970ef49924e04323409c9381d9f51832f131d5a280889e054ae4b1ca1f7240000000000ffffffffcbcd3e0532be3a3a350f55ead4b92bdc3792c45c76b092385a501ce16c3a69130000000000ffffffffa1f5c000c326e9621ce3b46650dfa11faea785031d11f8c00f15df7f4ef9c7270100000000ffffffff090807000000000000225120a8d85fb434b512e37ae7c33e0249f8e41727b0be3c6cfbb6207359eb2b3ad2992202000000000000225120a8d85fb434b512e37ae7c33e0249f8e41727b0be3c6cfbb6207359eb2b3ad2992202000000000000225120a8d85fb434b512e37ae7c33e0249f8e41727b0be3c6cfbb6207359eb2b3ad299407e0500000000002251200eab9eb1efff466c88a35e7d7223133d0884bed55d39740baff326a95b06074eef62020000000000225120a95b4f57570f54a164756f41ac5be9675548140075f29c9cf6f256eefa281a125802000000000000225120a8d85fb434b512e37ae7c33e0249f8e41727b0be3c6cfbb6207359eb2b3ad2995802000000000000225120a8d85fb434b512e37ae7c33e0249f8e41727b0be3c6cfbb6207359eb2b3ad2995802000000000000225120a8d85fb434b512e37ae7c33e0249f8e41727b0be3c6cfbb6207359eb2b3ad299f2de000000000000225120a8d85fb434b512e37ae7c33e0249f8e41727b0be3c6cfbb6207359eb2b3ad2990140a037525c1a40c3774cfc09ffe91e238db650cc87b642f56995ec2a5090d9c7dd9ec09d2ea69a884375f2b4b2359cffaa4056e435c08d516b83876d3b731cc841014066197453c4671ccef1abab5f3178228eae68ee27a47e50633bae88e06ce3e5fbee3216d7d3f1fd4c20add17e569aac12a47a12ff5a15e1c2ada16230833657e60140e868dad39f74c49d2c2f97ce6a11c722bb2ec339bd8070cb9deb5ec0e677e1c4b67b0339abb54f4c29ea1bf48d338e7f46c18f677c2ee322fcab96e05b05b92301416b91ad22771801b8a6dde9a171944e2490dfd69910f9f4dc6396b1123eb8e2c48dcbd65e594b2908c2bf051167b6ee4369221ca7df00362676011c708f9b3168830141e7454f9d5125344aed23f2561fca0bf1a78fdcbe600f7b043ed2ede91f1fb6a51ede65897022cc21577b3ac14a790b70b644254e3f6ff0cb6ac15eee711b96938301404564ff93247ee60c635133e8a17179a5c9cafa660c680ed338f7158e47f7c539c56c4cdea4e84d4a78a73f787d4aa4b189d3a907d85de291c930b9f3c5d7824a00000000
wTXID
dd331b0c2b16b49e7201158849c390ba8ac5258264845b98467bec8a5dfc45a1
The wTXID is the hash of the entire transaction data (including witness data).