0

litecoin-cli gettxout "9d56b3bf179a988873fc2162d70bba44849ef822764c9049a0f722b5fdc9acc1" 1

This is the command im using to get information about a transaction.

litecoind -txindex=1 -daemon -conf=/home/litecoin/.litecoin/litecoin.conf -reindex -rpcuser=cryptosensei -rpcpassword=foo_420 -rpcport=9332 -rpcthreads=1000

This is the command i use for starting up my daemon. with the -reindex it should not re-verify the blocks. So im wondering why im getting null.

If anyone knows what the issue let me know. Also here is the response of getnetworkinfo & getblockcount

getblockcount

litecoin@Debian-913-stretch-64-minimal:/root$ litecoin-cli getblockcount
0

getblockchaininfo

litecoin@Debian-913-stretch-64-minimal:/root$ litecoin-cli getblockchaininfo
{
  "chain": "main",
  "blocks": 0,
  "headers": 526188,
  "bestblockhash": "12a765e31ffd4059bada1e25190f6e98c99d9714d334efa41a195a7e7e04bfe2",
  "difficulty": 0.000244140625,
  "mediantime": 1317972665,
  "verificationprogress": 1.737314343731834e-08,
  "initialblockdownload": true,
  "chainwork": "0000000000000000000000000000000000000000000000000000000000100010",
  "size_on_disk": 2217395400,
  "pruned": false,
  "softforks": [
    {
      "id": "bip34",
      "version": 2,
      "reject": {
        "status": false
      }
    },
    {
      "id": "bip66",
      "version": 3,
      "reject": {
        "status": false
      }
    },
    {
      "id": "bip65",
      "version": 4,
      "reject": {
        "status": false
      }
    }
  ],
  "bip9_softforks": {
    "csv": {
      "status": "defined",
      "startTime": 1485561600,
      "timeout": 1517356801,
      "since": 0
    },
    "segwit": {
      "status": "defined",
      "startTime": 1485561600,
      "timeout": 1517356801,
      "since": 0
    }
  },
  "warnings": ""
}
0

Assuming this is identical to Bitcoin Core.

This is somewhat confusing, but it simply means that UTXO is spent. It is reporting "nothing" as output.

13
  • Yep very confusing. Also yes it is completly identical to bitcoin core actually. What im asking myself is what the exact difference between -reindex & -reindex-chainstate is. Maybe this is the cause of all of that – UnknownHex64 May 3 at 17:12
  • -reindex scans all block data again; -reindex-chainstate assumes your blocks are fine. It sounds unrelated to your question - there is nothing wrong here. The output you're asking about simply has been spent already. – Pieter Wuille May 3 at 17:13
  • Ahh okay. So what method is the correct one to simply check a transaction? [Confirmations etc] – UnknownHex64 May 3 at 17:21
  • gettransaction (only works for transactions in your own wallet), or getrawtransaction (for all transactions, but only works if you have txindex enabled). – Pieter Wuille May 3 at 17:23
  • gettransaction returns that its a non found method for some reason. Yet i have the txindex enabled and set but it won't work for me for some reason. You see that in my parameters to start the node i have txindex=1 – UnknownHex64 May 3 at 17:31

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.