db321065a367324a8ab2734f5a36b85b375a8197ff0cc4710e48d33448634151
Summary
| Location |
208,518 confirmations
|
|---|
| Inputs |
6
5,548,854 sats
|
|---|---|
| Outputs |
1
5,462,806 sats
|
| Fee | 86,048 sats |
|---|---|
| Size | 588.00 vbytes |
| Fee Rate | 146.34 sats/vbyte |
| Features | Segwit RBF |
|---|
Transaction Data
1
- Basic Transaction
Inputs (6)
Raw Transaction
| Bytes | 1,074 | 426 + 648 |
|---|---|---|
| Weight Units | 2,352 | 426 x 4 + 648 x 1 |
| Virtual Bytes | 588.00 | 426 x 1 + 648 x 0.25 |
010000000001067ab96e836bad9feed38a944092acbfd3a8525dcba164c798ccb1b066bcc0e6620100000017160014b4540fff8399d7ad6740ca0c9a25898da3f3d15dffffffff5cd7150950eb887f49d1ce6ac369b2aa8ad751c02c953019188ff990fbd14e760100000017160014b4540fff8399d7ad6740ca0c9a25898da3f3d15dffffffff5f6f55891ee56b086f04977273c06f5373066a96e3e01b59a306714bb9d743852100000017160014b4540fff8399d7ad6740ca0c9a25898da3f3d15dffffffff8a8706eac674a81c714692e2da82d91584d19e8006411104ba087fcdd45dbda00100000017160014b4540fff8399d7ad6740ca0c9a25898da3f3d15dffffffff4c814b05a89f7c144b1603514fbe9e58e071468f442ec6eb862a361b30f931c80100000017160014b4540fff8399d7ad6740ca0c9a25898da3f3d15dffffffffed8c09a857afb508ba5d401a378150356fb74121258da309b893c459c1207cdc0100000017160014b4540fff8399d7ad6740ca0c9a25898da3f3d15dffffffff01165b53000000000017a9145b4436f06522b963be1cabae907f6528e1905b1b8702483045022100998cafec8bed1a4d31cc35628f9e99882561defcea109c132596d633112ba14d0220446226faefd5f701e274d3471f7134c3d3c9c042918b854a3b96eaab9e315583012103fb9a3c5e59be42eb09aedb85a316314ed43d2b8e4339083a0058b9af54a0a73102483045022100d9e03a46fc857c53c2443d8f8752bc79f7c366f760a565637d2f5203ae40c7cd02203fe5dfba5c22830fc195bddc55f5d619ebcc7f04caf888729725fe8e7400cffa012103fb9a3c5e59be42eb09aedb85a316314ed43d2b8e4339083a0058b9af54a0a73102483045022100921ee4d84265975c17294c7829b0103c11cdf66034d5f0903e74661d72041ca402207b1e8fa92f64af197ca5e1b894b93183ce7cc81933bad306445a7d76c24ef35c012103fb9a3c5e59be42eb09aedb85a316314ed43d2b8e4339083a0058b9af54a0a7310247304402207ea06d7a425db58cdd453e9c53fe27f3f758bb6e9a30dc88710c04f23ffb17ae022025aaed96aaba409498fdd8006e9e2b8224e6e97c96595068dbead76ee29b9a62012103fb9a3c5e59be42eb09aedb85a316314ed43d2b8e4339083a0058b9af54a0a73102473044022049e58ac121da9edd2c68509ffbdb91c0d9455bc86b55a2de96631c29b59c78b2022069c34ff35dff86637ae36ad97568f8a5f73b6872585597f8fb7dd37fb60e305e012103fb9a3c5e59be42eb09aedb85a316314ed43d2b8e4339083a0058b9af54a0a73102483045022100d27e960a4d4a9af0ae0944dd16b9beddbec0c0a3ce1c906a198f948610ba05f102206f50696a60001beb17d2ba12111a5abe93f6c9caaefa961cc5ea6d6f0de43585012103fb9a3c5e59be42eb09aedb85a316314ed43d2b8e4339083a0058b9af54a0a73100000000wTXID
fae1bdbb6dfe139515ac5bfc6b999ad642736b2131cc14a0c9c483a12fd39224
The wTXID is the hash of the entire transaction data (including witness data).
