71f047d567c65c443ef46c5934d86455fb56025c562415dba57e65c1e263de4d
Summary
| Location |
213,995 confirmations
|
|---|
| Inputs |
6
22,760,599 sats
|
|---|---|
| Outputs |
2
22,724,839 sats
|
| Fee | 35,760 sats |
|---|---|
| Size | 595.75 vbytes |
| Fee Rate | 60.03 sats/vbyte |
| Features | Segwit RBF |
|---|
Transaction Data
1
- Basic Transaction
Inputs (6)
Raw Transaction
| Bytes | 1,081 | 434 + 647 |
|---|---|---|
| Weight Units | 2,383 | 434 x 4 + 647 x 1 |
| Virtual Bytes | 595.75 | 434 x 1 + 647 x 0.25 |
01000000000106597fbf5f596fed980ec354f5e21b21d56d56d530ca5e58274fcd181e1ced955a00000000171600146351bd65d4f2d92355fabdbad1f9dfe50b5560e9ffffffffd168c6761513d6c1ed3656cfef808ce12066db3313ffc714bc28b650617aaac900000000171600146351bd65d4f2d92355fabdbad1f9dfe50b5560e9ffffffff14d1622b9d976745be9c2cf05ccb91d8f83e1128ea435a87b231f18fcae0f99200000000171600146351bd65d4f2d92355fabdbad1f9dfe50b5560e9ffffffff834f1ea1d5e6ad4e544989a3d21e973d7d01341acd7620a00ca5366d3620cdbf0000000000ffffffff5451f9f9b909c1bfade5dd7ea190fc161e0b8d7c8e340cb3990fd4acc37e729800000000171600146351bd65d4f2d92355fabdbad1f9dfe50b5560e9ffffffff2220ab296c5fe7e1c45b4d85edfa6ad70790c7f46cf66c28b5214ef06bce45b900000000171600146351bd65d4f2d92355fabdbad1f9dfe50b5560e9ffffffff02e05f5a010000000017a914b6253b71e368699c8a47a8fc4b81c13d623cc3798707610000000000001600144309cd6a171e2ab2aa46b43e0803b228449bc5ef024730440220352bf8d96f32197fc0b619b1726e4c506a73a3ed3aabd0d1395d05b59aa1951302202f374e66c986f393e85803b82327cf50dd8108c6d23756ea43b40e6646d5c4d2012102a57d9ba70087c397ff63d07b2ac8b35e008ddb76f78fa039c3384cbb7ccf9f7102473044022063326de557d094d949258688205fd33f981d702217647c1c53f4b636ec71c94e022026dca21f2f7ce2f6520f7281eb45ea8e292d4acc5fdd32ced47dfee0e2fd1fd3012102a57d9ba70087c397ff63d07b2ac8b35e008ddb76f78fa039c3384cbb7ccf9f7102483045022100c5c243dd5bfd77289f141033612dc5882580a95a4e91b1289d2f2d91a77416cc022001b33108322fd651ea87fe9363b18a5c7cc807b025438e20f996c7e74e97016f012102a57d9ba70087c397ff63d07b2ac8b35e008ddb76f78fa039c3384cbb7ccf9f710247304402203dcc666f56ef9d546e17269fefe95001648ab1f450b4f0aba95fae6b2f99a907022055e8cafc26a8ed7a1006bcbd9b113f16510da33212d75671c479a3606b6a7184012103196a7def0e46b1e8a526bf9cc815f60969d4459f318cdcbc53f86c8b3dd8e73e0248304502210091aeafd6922478f9c1767bc67a94c4a2ebd1eb893e2e3882e18f993c7c4b175102204f407e54e70346ca5177357390000387a3e30638d9f8f51e8a1b1fe160944f78012102a57d9ba70087c397ff63d07b2ac8b35e008ddb76f78fa039c3384cbb7ccf9f7102483045022100fcbcb43f8a01493c0b7b1fc11132105419704c54a64e312875b1ecc546ba747f022071c72837637953fce87b192431fc6ffed03efc33f889980f77116d4b7332c912012102a57d9ba70087c397ff63d07b2ac8b35e008ddb76f78fa039c3384cbb7ccf9f7100000000wTXID
5f0f41ebd00ea079ac16d80757047432062a2fd3b4a2735e5d96e0fa23440f18
The wTXID is the hash of the entire transaction data (including witness data).
