0bd2b27a083ce9dc904fb9b9debbd3d98a16b5cafb4f0fb5a7a6e5b059f073f8
Summary
Location |
277,049 confirmations
|
---|
Inputs |
2
154,188,254 sats
|
---|---|
Outputs |
14
154,174,255 sats
|
Fee | 14,000 sats |
---|---|
Size | 698.00 vbytes |
Feerate | 20.06 sats/vbyte |
Features | Segwit RBF |
---|
Transaction Data
1
- Basic Transaction
Inputs (2)
Raw Transaction
Bytes | 1,079 | 571 + 508 |
---|---|---|
Weight Units | 2,792 | 571 x 4 + 508 x 1 |
Virtual Bytes | 698.00 | 571 x 1 + 508 x 0.25 |
01000000000102deef67630f8cff40119303fa8f6b93da8ece8d19b2ef6c728386a937d83cf29d0d00000000ffffffff05fcc55fbaf90825fee31d3942d88f8e99107ec8d76593cb90bda88d64ee96ca0b00000000ffffffff0e21ba0400000000001976a914a6a67c19726d6895332bccbdc4478dcaa24a6d1c88ac62270900000000001976a9144ec83f5dba2ca2da71854615a1d8a4e331e545db88ac2edd0900000000001976a914a7d533f9ade4c8fb4e0690a49fe767ad93eaee1f88acd18d0b000000000017a914b55ea1ae62dd7eb32f7fa3002bced0da7a2cde4687f8791300000000001976a914ecadcc9cb969f1f81d6fc45973b0bb958fc289b088ac2d7416000000000017a914de47046d325758e51f3d1f4b447d3494548cd97187b3192700000000001976a914db7bce0d3ba997affd652c62f6c3d505227608ea88ac80584f00000000001976a9145d46b0c1f89e6b503ed6bab44588a6daeea16f3188ace43565000000000017a914d55a34f723ccde5bf380011ac7db09fd86a53beb87e0c2c300000000001976a914ea139a8a9ef5fa735a296c7326c842bfa935adfa88ac2729c900000000001976a9140bd8553267bb569f70c36fbf75a94f367d32e97d88ac33080401000000001976a9144cb4981c0b704d2652049ef6e3d4a9e583b8319388aca4858801000000001976a91494317189a1b3ae739632edd5094cc1f7a080d6a388ac9326ee0300000000220020d96a61c51ecfbcad6b7ed91508b5be716a094434c69ddc3b1748d90077f619060400483045022100c92543abd66280a363ba277ca316bf9cba8bff464fc4c9a25015f30e055140c0022020d6445476684b927649cc088d6103acbcdfdf2ce3c7aba50fcf6cfef37f90210147304402200ad9790d077ddff98b071087cffb9a2afb482ed7d2bba7dd85046e240ad888f9022051b5b144d25f6f9c28b4b795b4959caef382f0a3abd14fe61350d1ad44c20d8a0169522102d9c3d1fcbf0baebe788776dab11830981a67aa2fa32c74b5b1a8982554e5f5202103cc666bd509fbb1fa242d7de39df97abe8d484216e31cc13a136a9bf366a708cf21028f87c24043ab80364f24c3b9e6b7b557d34153ff990cb927a1e5c10f48f35c1953ae0400483045022100c9357d4c1d8874154b30250f83732f432f174ea5b0442bed5b096b72e0ab8e5002205441f3f2e6fb793d1fc0c78cb842d25a468697718e7aef917f156a843142cf880147304402204cbe43eec3cfde51cda3740e40bbc08488cec29319a1268a0d0d105ee778650a022055e7786747490326f164d98eeab0783ebf8183b6a44ef3f13e7d47adf9553d2301695221032a95828ad7ff0ebdac9d253ac0582e347eab8b5ef4c8b009004821d62e4aaf472102e9d2306be1a51565c5a8c14dce3c9d617c2413f00a6ff15f935946891415aeaa21028a7d3756e589d02b2e85ba653d6f57b932318361c127035b243de4a626ae396753ae00000000
wTXID
2c12b2e6b9ff0bfc7912904bf72c7bc77f64711be8cb1002eda60e2b1d6d7086
The wTXID is the hash of the entire transaction data (including witness data).