198ebf109875f373f252b4536ef261593c09cc87e1ba9bb2f0694f54202a39bc
Summary
| Location |
168,533 confirmations
|
|---|
| Inputs |
5
2,252,458 sats
|
|---|---|
| Outputs |
3
2,174,661 sats
|
| Fee | 77,798 sats |
|---|---|
| Size | 561.75 vbytes |
| Fee Rate | 138.49 sats/vbyte |
| Features | Segwit RBF |
|---|
Transaction Data
1
- Basic Transaction
Inputs (5)
Raw Transaction
| Bytes | 966 | 427 + 539 |
|---|---|---|
| Weight Units | 2,247 | 427 x 4 + 539 x 1 |
| Virtual Bytes | 561.75 | 427 x 1 + 539 x 0.25 |
010000000001051afa4a1f5a3c2f71ff787f9333fb1e0825970d7018512a9f8073123cd87b0c7f0100000017160014a2879106f2375f2406ddcb7217ae8eca81194364ffffffff54f6e50238f30996e2f54255d410626758c8c8f621ddb5407df34583ae19ddb708000000171600141710005e7222f921af5daab25bd34f8be45eefc0ffffffffa4d7ca3c1f85fec29152666e5d9f592402e8d893f8862325ebca1552dd7c258e0100000017160014a8fce2eb961f6c6aaf6702529ec2f6f2dc47b8e3ffffffff101472bf917902bec116c09a3f42ac27c59b721c51c4bf286c783a2318bcd3240b00000017160014ebbdb19957580dc209d7a2b212cf784d2af4a18cffffffff101472bf917902bec116c09a3f42ac27c59b721c51c4bf286c783a2318bcd3242400000017160014b8d8d87ae197a1f0d7498ad1d974060e39a0ba7affffffff038669010000000000160014e3c98af27948c79490854f3f45b93455694e12e0fd301000000000001976a9146cbc6cf5fcd0ab9ab18880d6d13f62ab560f8a9188ac42940f000000000017a914e02948daea4ab0a4a5223e038c78db1ca35d6bdf8702473044022037fe9abf7972e8d19af901cd6d7a038cc9379f88942e07af2a0f4ad053b105c9022065898c167eafc12d382dd18e750d93d79a91129f1cea7c043ed68d100f3e5e500121034fb3e6a625723f72338ab73dcdc6e53b35064d5a60fda625a1f7b6050217ae0102483045022100ac5c267331f9a975eb65562f6210df366764f5ded799a2f4c7b36789c3432c06022065a5a01ffbdf61e6831ec4ae6215c25a4c3e6bc5a55a531fb543f7277afd226d012103a2a216f51bffb5ee59652b0a4b5f748596ad5fa0b870804845de47fddc06ac800247304402205b5f083c5ad1d0a6791a45b15b3add4a99209619e1fb79c6187c0bef4d31a22202203fc1ad23099403c24804d3482f1c8520deb397acca20eeb5eb3282c89cef0f49012103f7a8eef50697425573127fd04f50ab2fb8ca942f4864d405f949835adf5116e402473044022074b2e97fe9dc08366599345b25326a0fad0926070f9a16f0aa32aad4c295dfa802206604187185e1f1b8b9f4857a3f53486db59d7b9a12a2bdd92f532cbde740a9b601210304b1eb898aa28d0517c2a567d876b61fa7015a705747c4fc246438102382eb3b02483045022100fd774345ad666c744ed56fc72c31cf8bcf0f349c3b311c6f4ce4c62ac45d260b02201719d8a154514bb6cd3dc186ed9681f76ff3717f8513be8f6c87596f92e4ac1b0121033a06dd3011f6fb0bc365e47b0d5029d3cafb1c74e092cff1597a942a0eb97cf500000000wTXID
d0ad543ecbd3aab5edf8e84c10ed45a260e883587c029615a2e5cf088dd84048
The wTXID is the hash of the entire transaction data (including witness data).
