bd5d6fc6a8f6701a68449239b4b58e8dd5ab0fe6e09c21abb0ea4b6b07bbb41d
Summary
Location |
63,213 confirmations
|
---|
Inputs |
6
489,300 sats
|
---|---|
Outputs |
10
458,260 sats
|
Fee | 31,040 sats |
---|---|
Size | 775.00 vbytes |
Feerate | 40.05 sats/vbyte |
Features | Segwit RBF |
---|
Transaction Data
2
- Relative Locktime Available
Inputs (6)
Raw Transaction
Bytes | 1,075 | 675 + 400 |
---|---|---|
Weight Units | 3,100 | 675 x 4 + 400 x 1 |
Virtual Bytes | 775.00 | 675 x 1 + 400 x 0.25 |
02000000000106ff75e0559a6783715ff6c991438d65928f27ad130c41bfc45d1a06b7d48d9f660500000000ffffffff0f7c1af9217b316cf2ee2a7ab6f1f06629ce8428145586acea1987050822d2560500000000ffffffffff75e0559a6783715ff6c991438d65928f27ad130c41bfc45d1a06b7d48d9f660400000000ffffffff84fa6abc88650c3372a53b995ec3eeddb7394ddb73c9941f05094aff84f835670000000000ffffffffd3ba3e782ac86c2d3a84c5f7ae69a6a8b21a77a0d65843e3e0a39a7b2da2dfdf0000000000ffffffff04edd4cd7c6b3341dc29873a213d7b8cdc09f860c73c7c09799ae079cc7f97a00200000000ffffffff0a080700000000000022512063ba352a7399211cbe0b016e25f122924c2c0d0f05cd8f43dd7e61eeff50e9f6f40100000000000022512063ba352a7399211cbe0b016e25f122924c2c0d0f05cd8f43dd7e61eeff50e9f6f40100000000000022512063ba352a7399211cbe0b016e25f122924c2c0d0f05cd8f43dd7e61eeff50e9f6c12d020000000000225120d0011228f799d4364a15b168d185c5e2da0b9355f2a9fc31132c787d108086bf3041020000000000225120bc2fd71880f071c942d0e960a9fe48e65cb2c87ce19f334bbe62365c9a2680896b1c00000000000017a914ea6b832a05c6ca578baa3836f3f25553d41068a587580200000000000022512063ba352a7399211cbe0b016e25f122924c2c0d0f05cd8f43dd7e61eeff50e9f6580200000000000022512063ba352a7399211cbe0b016e25f122924c2c0d0f05cd8f43dd7e61eeff50e9f6580200000000000022512063ba352a7399211cbe0b016e25f122924c2c0d0f05cd8f43dd7e61eeff50e9f6c06002000000000022512063ba352a7399211cbe0b016e25f122924c2c0d0f05cd8f43dd7e61eeff50e9f601407842a6c6288ae500087ef0463b4e202d003725670d4afed0143588edba91464e060652e2b3c1a879ad43d394e241e7c4046874d4b28ee2efe9ac0faecae8aa3e0140408af8c0d213ab2ddccec4a748c2cf53915b998f5bfab74c9939f2e258942c9cf5e2045ab2254e1d3a2aa72fb46b664f4c4a10dfd649ce14b3fbd2215ca2292e0140651dfb4ec86ad3d643ad7c8bf9c6f5bf6711b8f9edb85cb895cc90ec7eb6452e3861120bcee8a3207de3a5247a3d257452aaf86a28dbe11f12ca70eef4475ba4014103d69a30501369c4681df72fa948db844094d27abb9f6283f574b85865d36b28bde14d9c97f86f05a2f64ea258d5542f8bb8798f911ee89d0da6a6837e43dedf830141dcb07183e2b5a583ea4b4056ac6a80f7d35f5a3792299e8683054cc57d4b0f3eedb80a282e25fc2feafa51df75ed8f7442d808769eb55550fcec7ea8da38a5a98301408a8eba5c0d61334b65b22b718290351b46198d5524ad5b9b9ecf9c3c827c76327728c062727be8e378fc46595778f6577957906ccf17b09801e2373efb45c05a00000000
wTXID
bf1077d2e98d8cbb838c3fa9c9c5e85933127faa4278c747faac36421cf30c8c
The wTXID is the hash of the entire transaction data (including witness data).