Welcome to the Dash Forum!

Please sign up to discuss the most innovative cryptocurrency!

Is this a mixing transaction?

Discussion in 'PrivateSend Questions and Help' started by jimbursch, Aug 14, 2017.

  1. jimbursch

    jimbursch Active Member

    Joined:
    Mar 5, 2017
    Messages:
    561
    Likes Received:
    351
    Trophy Points:
    133
    I was looking at a list of transactions in Core (./dash-cli listtransactions) and I see a bunch that look like this one:

    Code:
      {
        "account": "",
        "address": "XeW5sqEj8FBTfM448qBoYnw3By5HMioDeb",
        "category": "send",
        "amount": -0.01000010,
        "vout": 4,
        "fee": 0.17000170,
        "confirmations": 7106,
        "bcconfirmations": 7106,
        "blockhash": "000000000000193c244d3f02906ac71e9f349d9b6fe97f8c8839cbe868f58fcd",
        "blockindex": 6,
        "blocktime": 1501608552,
        "txid": "be048ba19bd4aaec97fa41719049455746fb86f1854fd7a310d74e7f4f445d06",
        "walletconflicts": [
        ],
        "time": 1501608492,
        "timereceived": 1501608492,
        "bip125-replaceable": "no",
        "abandoned": false
      },
    I'm guessing this tx has something to do with mixing. What I'm curious about is:
    "fee": 0.17000170

    Can someone explain that to me?
     
    • Like Like x 1
  2. UdjinM6

    UdjinM6 Official Dash Dev
    Core Developer Moderator

    Joined:
    May 20, 2014
    Messages:
    3,300
    Likes Received:
    3,272
    Trophy Points:
    1,183
    Yep, it's a mixing. And it's a bug - wallet assumes that if you spent some coins then all inputs are yours, which is ok-ish for normal txes but is not true for mixing ofc. Looks like the same bug is also affecting gettransaction and probably some other rpc commands... Created an issue https://github.com/dashpay/dash/issues/1574
     
    • Like Like x 1

Share This Page