008efd9fa6a5b3911a59e75cc8f6f156c868bdbc569ca1580ee366dc5a6f51a8
Summary
| Location |
604 confirmations
|
|---|
| Inputs |
4
6,989 sats
|
|---|---|
| Outputs |
5
5,384 sats
|
| Fee | 1,605 sats |
|---|---|
| Size | 552.25 vbytes |
| Feerate | 2.91 sats/vbyte |
| Features | Segwit RBF |
|---|
Transaction Data
2
- Relative Locktime Available
Inputs (4)
Raw Transaction
| Bytes | 1,075 | 378 + 697 |
|---|---|---|
| Weight Units | 2,209 | 378 x 4 + 697 x 1 |
| Virtual Bytes | 552.25 | 378 x 1 + 697 x 0.25 |
02000000000104ca0b0fd5812f790d4583f9d472171a6a1bd2684be9b226850708297d4a62743d0000000000fdffffffca0b0fd5812f790d4583f9d472171a6a1bd2684be9b226850708297d4a62743d0100000000fdffffffca0b0fd5812f790d4583f9d472171a6a1bd2684be9b226850708297d4a62743d0200000000fdffffffca0b0fd5812f790d4583f9d472171a6a1bd2684be9b226850708297d4a62743d0300000000490700800522020000000000002251202ddc917fdc8a09e07fc067193c7eed937fe30eec226e810f0f2e5f0906c0251622020000000000002251202ddc917fdc8a09e07fc067193c7eed937fe30eec226e810f0f2e5f0906c0251622020000000000002251202ddc917fdc8a09e07fc067193c7eed937fe30eec226e810f0f2e5f0906c0251622020000000000002251202ddc917fdc8a09e07fc067193c7eed937fe30eec226e810f0f2e5f0906c02516800c00000000000017a9142a87cf5266f6a9f327bc30cb65ec2a309f28f046870340147546fad80f301ee8a59fd0a7cfd5abc86d2373b48987ac23914b44d8326462e8abc65d3d03418435fced2921b5a86643ed031389643f7ab13fed0ea2994279222048cb7fc634e7046df3c2e8f7f5a51db117e7db9b91cde6153fe6b276b674bc93ac21c048cb7fc634e7046df3c2e8f7f5a51db117e7db9b91cde6153fe6b276b674bc93034016c0aaaee27e704326211c0a1814eacbf18a9433db371b30693ad1bac6ad46bee33414d5d8ff4763cfbdfa978342976b0f3b23df6ee99283c38b48d9223e1752222048cb7fc634e7046df3c2e8f7f5a51db117e7db9b91cde6153fe6b276b674bc93ac21c048cb7fc634e7046df3c2e8f7f5a51db117e7db9b91cde6153fe6b276b674bc930340f15337b388e7a26855a06f379d159449925fcc847c92a2240a719b4b4e25cc4f4d98c1b87aa64d344ab6911fa00c2528748d308deb0ee520bac9812cc53b0475222048cb7fc634e7046df3c2e8f7f5a51db117e7db9b91cde6153fe6b276b674bc93ac21c048cb7fc634e7046df3c2e8f7f5a51db117e7db9b91cde6153fe6b276b674bc9303400a020151893ce7a19852e86b5f699d3fe37eb86302722df8836759df58fd16c0f4069ee7a7e8741c5a0e3076738a3905d74b149bb2525de807660865a7c8fc1ebd2048cb7fc634e7046df3c2e8f7f5a51db117e7db9b91cde6153fe6b276b674bc93ac0063036f7264010321625de3c83352d97207414ae1a82ed5d45c84a76a22d9a609251c1acbe7b03b27f80103221f7ccadc281fd49fbaca2794f715f5bb6aef8c62b4773b502589f74cca6a892437020103218bb2942d131f74c8fe0c3d8213fd375760090d49533bf57a50ef7383086817f74401020266065b20c2db6c7e84e3d95b356991ecddb7698c7aadca77299a502e9ceafbb73419ad796821c048cb7fc634e7046df3c2e8f7f5a51db117e7db9b91cde6153fe6b276b674bc9300000000wTXID
a7133a99893413731c8654d034d5315a12efb9929f84d3be91bd264cd31d7b4d
The wTXID is the hash of the entire transaction data (including witness data).
