74c47afdbfc20114305f743cdfa15e26b219a0cf6a1064296e60a43a7274ae71
Summary
| Location |
205,428 confirmations
|
|---|
| Inputs |
6
145,345,999 sats
|
|---|---|
| Outputs |
1
145,331,984 sats
|
| Fee | 14,016 sats |
|---|---|
| Size | 587.75 vbytes |
| Fee Rate | 23.85 sats/vbyte |
| Features | Segwit RBF |
|---|
Transaction Data
1
- Basic Transaction
Inputs (6)
Raw Transaction
| Bytes | 1,073 | 426 + 647 |
|---|---|---|
| Weight Units | 2,351 | 426 x 4 + 647 x 1 |
| Virtual Bytes | 587.75 | 426 x 1 + 647 x 0.25 |
01000000000106f3ee6017f62b048dec38299207c54a9fb78ddcf946ff3eb299aa70a879f61c9b000000001716001436c76668d55e9c36ab3164dd1de68513077c3d23ffffff002647f4a46ef2d8391cfbdb195e98e4ba638a13888e49db4162d685c3c79086b7000000001716001436c76668d55e9c36ab3164dd1de68513077c3d23ffffff00c2c830131f4ee5793f3d7fe78668f2d4e6ede467d0c408e5803161ee5955b999000000001716001436c76668d55e9c36ab3164dd1de68513077c3d23ffffff00e39174bec8f98b1d1d321db4bdae02c992b597bfd4d7c610a4042830e4d25641000000001716001436c76668d55e9c36ab3164dd1de68513077c3d23ffffff0005bb3becf111a5b5c73d28e3ea9705840eeb7b5419f44bce3fc403ab6f29a4fa000000001716001436c76668d55e9c36ab3164dd1de68513077c3d23ffffff00c876eba41421b53246680bc23ec9627a7b661448bdf4517c3ddb6428adc8b68c000000001716001436c76668d55e9c36ab3164dd1de68513077c3d23ffffff00011097a9080000000017a9140c219f2da28eb16ab8b115b04d8e9799a11183688702483045022100f00f9c2a3a93bf228efcf7d847908a245d1b4cd1897eabeed690f39ad3fda8670220370f97b05add310c0ff59e4ba12f58a1c79c4bc5f50701b52c003a7ead2c67b30121034e7116ee5b2b6e9ca58b4d052419c5997ec2907c679b6ee2a52b2afd5220e26c0247304402202fbf87e3638b660f67c91bcbe5e32add45d4bd8532c10a982fc0fdf07f05970602207893e4078d37d3754fb72d6b57d6c9ab254b9a7182e581bddaedf43e421ab3790121034e7116ee5b2b6e9ca58b4d052419c5997ec2907c679b6ee2a52b2afd5220e26c02483045022100ab71532f6a3f2c93621806cd16c2fb6f809cccf269817300b9dbf04b1bf48ae00220329481fd9d9aee281f2c09294328591036cb6dc29bed463ee10b7235e441c4460121034e7116ee5b2b6e9ca58b4d052419c5997ec2907c679b6ee2a52b2afd5220e26c02473044022022bfe862e1965794e045daab9f09a53166dcec5f994a6cd69b96522e5a924b3e02205a4822a0af9efdcdc98749d4e3825cfe0b4a81f0eb38d24441a10b80686265480121034e7116ee5b2b6e9ca58b4d052419c5997ec2907c679b6ee2a52b2afd5220e26c02483045022100f181b6d99367519cc042bf6765397aa2d6188fa76ce273af89f6e34a11110d8f0220305c567b52c177a7c9b31e154dde75f4dc67f360b3504f6131c26e9ece9adafc0121034e7116ee5b2b6e9ca58b4d052419c5997ec2907c679b6ee2a52b2afd5220e26c0247304402206acb4f5853207fb37357b058442bf234ae7f7a8e14a4378b374000b1c43f89950220234e8f31941e0f84f98b92c68cbdcb2fc33d3ace151189282927f616307739790121034e7116ee5b2b6e9ca58b4d052419c5997ec2907c679b6ee2a52b2afd5220e26c00000000wTXID
03d583706f61b0b1f73530e9cae34fa6b3788088f1094d94ff79dbc59179e67e
The wTXID is the hash of the entire transaction data (including witness data).
