64a27faba3f1ce2a1ded5bfecda8d93234609d7cba9762cdb3ab5e405d68399d
Summary
Location |
306,692 confirmations
|
---|
Inputs |
6
200,754,378 sats
|
---|---|
Outputs |
2
200,743,970 sats
|
Fee | 10,408 sats |
---|---|
Size | 570.00 vbytes |
Feerate | 18.26 sats/vbyte |
Features | Segwit RBF |
---|
Transaction Data
1
- Basic Transaction
Inputs (6)
Raw Transaction
Bytes | 1,077 | 401 + 676 |
---|---|---|
Weight Units | 2,280 | 401 x 4 + 676 x 1 |
Virtual Bytes | 570.00 | 401 x 1 + 676 x 0.25 |
01000000000106429d1b95caf4ff4a10e56a752bcbe75de441da75e44cc6596df6daaa45f799080100000000ffffffffd0647e1435209369330e32ec5e0b39368c70c996dc65f79a0439e0e20790a0580100000023220020f78d8fb58c802f94b83ea9c71f10935f73397089551d1e14b90fae27fff9787affffffff714934a8dbbf9b9eb7c188d2326bd3f8d77c18f7c7fb5ee96173932a3eb98ad50100000023220020dd9d87995c9a96f5c919ef383836283bd1f842ea3133acd6c4794ae938c7c0fbffffffff8a5b9ca6d6ec4f161d2e99c8c17c463585f77430cc7f7944ca4c734a337501e10100000000ffffffff28f727b5eda98f0e7b38fdb5e11acc85bfd71cead24f18ff698b93b30c359beb0200000000ffffffffa409da6e96d958823d0934b477d5da9bf22a4dbf93c86fe0c5fc39266803a0ee0100000000ffffffff0281aede010000000022002004818e1b700d40f1b360c1ab26ce480e396e114add70d28cf94d23c88b602b1ba16d180a0000000017a914c54e2889d97032b3dd9ba6eafaa923ba238e25f68703004830450221009676f94f9ca5d1336b9a404538cf0856eb019b9805d4f6730529939e5731d15902207e107b4eaf0f97a400e3b8325862a7d82911347a331d085c4edbff389e0d18890125512102eae4524fd674b150e86988d1cf4c2cb0464d59a6ae9c00e22c42fd96934a14ff51ae0300473044022040ad34753730cd35d9fc940820965eff1df11e6679eecda344f52af6ab27a08f022045d286341ec65a51167be5a4414b049a0c2a4f760690f251df42630e4f6bc5650125512102d229bfa4045a83f952e82713f0e33b466504e74ec661b2a7067b9313f7dca37451ae0300483045022100a972f5af263a2254e7dc60ebbfdc5d244641e3ea5e6614b1425944dd2958f65902206e8cdf7c9ce9e5742dbec279f82ca2141ac681d4b1d2af6a949cd61fdbe689d80125512102d94d0d56616728f23c5ad27ee64c74d7592e8cb1c7fe5fa9ee0d418e4e0149f551ae030047304402205f3833918575c42717d2a32948953c58423a3b1d5173052913f48f9d78bb33cc02202e2fefb9d0d43f6e846f93d4fac54ae1f2fb84ae11d480935e1519bba242ead00125512102eae4524fd674b150e86988d1cf4c2cb0464d59a6ae9c00e22c42fd96934a14ff51ae030047304402201c6b1edbed3ac2c816e5de6c79254f52056c7f5025732198478a18e4dda5cc7a022032025efb1cbf6c156951a2a01311bd705390df57434e0ca6d867f848f23644d501255121032067f822d38181b28d3ae4ed72a9c53ad912896f848e0d44da5631005b47ff6a51ae0300473044022041084b07c4364e858881cf381a1e08a0ab06ca73976d9fcb2dbdf957637d10ee022041a57b3dfecb7dc7c9e118e72abfd0752c2191b3eb4e16e3508568e35d7419580125512102eae4524fd674b150e86988d1cf4c2cb0464d59a6ae9c00e22c42fd96934a14ff51ae00000000
wTXID
1fefd2fdbc4b9892b65e88a4c66f58fecba284af71c55059bba238ea944869b9
The wTXID is the hash of the entire transaction data (including witness data).