dbf2efefb6317e1a86ff96c4283835c3b85af8b746e2c1048a261a4b20fe6006
Summary
Location |
119,545 confirmations
|
---|
Inputs |
6
2,859,168 sats
|
---|---|
Outputs |
1
2,852,569 sats
|
Fee | 6,600 sats |
---|---|
Size | 589.50 vbytes |
Feerate | 11.20 sats/vbyte |
Features | Segwit RBF |
---|
Transaction Data
2
- Relative Locktime Available
Inputs (6)
Raw Transaction
Bytes | 1,074 | 428 + 646 |
---|---|---|
Weight Units | 2,358 | 428 x 4 + 646 x 1 |
Virtual Bytes | 589.50 | 428 x 1 + 646 x 0.25 |
020000000001067269ed3a1bde8bffad2dcd0d48955385bcc0d42d26bca4b50f6e399d0d2440744000000017160014b4875bfc73335a3e557f6139d63880eaa6d2fe23ffffffffdd8544e37ec9f18ac352c7758f9d5e168c6264cdd8bc7597b57877c69f65e65a7400000017160014b4875bfc73335a3e557f6139d63880eaa6d2fe23ffffffff9d9eb020ff7be7909ccf94df064ffb67f8423753534638cb1f39d7bdb83bdddd7c00000017160014b4875bfc73335a3e557f6139d63880eaa6d2fe23ffffffff59cf4b3e1ea22c2a3f5aab5296decc9e58c3e512038d8227d4fb01653d6ecb7f0a00000017160014b4875bfc73335a3e557f6139d63880eaa6d2fe23ffffffff0f441ca152153d6b96d2ffebf1eacc88186e99a01f7fb8ff103265346da98b8a2f00000017160014b4875bfc73335a3e557f6139d63880eaa6d2fe23ffffffffddc16c7e1dffba8a492763517ed3a2012af5bde9884b52d0dc49c48ef05ea7939100000017160014b4875bfc73335a3e557f6139d63880eaa6d2fe23ffffffff01d9862b00000000001976a914335fc39b0217238a90a9c88a20acf75003afc10088ac02483045022100add12183cfbc9198c5e86ef0d5b262c3029a4a82469aac1da05262f2c1f430e1022029b406237a580ff27b34d65b94d1e526d8e4ae0c60144c91c437c9e9e5fa7a4f012102a35ff23eb0bfd8b0d13e123350a3d9362a9f41fb2582f8f1e1a2705c6ac5ea45024730440220439b875bde6be9617912c692456530fa05d1c2e5ae68d9a8dae7822d62f2cbc00220704d63561d206f0005b84637aec84001c39b281146ee120e50b5deb7b0a2d47b012102a35ff23eb0bfd8b0d13e123350a3d9362a9f41fb2582f8f1e1a2705c6ac5ea450247304402201cf6f56fb0247f329aa914d0c2cf8e7fafaabcfb8cc254bf2a1a4eaba441336a022075cd1f49efc0128013960da35e746f49aa66f157ea55a829ae42c84f1a071207012102a35ff23eb0bfd8b0d13e123350a3d9362a9f41fb2582f8f1e1a2705c6ac5ea4502483045022100af158192131298035dcfd7a4c4aadab50edd3c66e7e7968adaad0a0958e8797002205de4c8f8c0eee76e26e6603b6dd17f21838844dc970f355e9c4e1417223f479c012102a35ff23eb0bfd8b0d13e123350a3d9362a9f41fb2582f8f1e1a2705c6ac5ea450247304402200a2dca51f0099f2b5c4efde85399a285abcd98e5230faff5aa30e9ff087eb759022040aa5d500d48e95c90efc7cfecdf6e33e91c16d5d953b7b3b9357b7d4ca5461f012102a35ff23eb0bfd8b0d13e123350a3d9362a9f41fb2582f8f1e1a2705c6ac5ea450247304402205e1b06bada0ca3a5b3c8da721542cd733a6e264b6a484507a8b0d32f27fabe360220525f9cd76a609efa66911ce6aad4b5174208e64b8acbc51ba53f35c69be2295c012102a35ff23eb0bfd8b0d13e123350a3d9362a9f41fb2582f8f1e1a2705c6ac5ea4500000000
wTXID
b72002e50c6df7ec8ff3fba91ff650b6202298672ec4087e6767785939bc911c
The wTXID is the hash of the entire transaction data (including witness data).