Why is the value of the input way higher than the output resulting in a second change output? [duplicate]

Why is the value of the input way higher than the output resulting in a second change output? [duplicate]

This question already has an answer here:

Background: I'm experimenting on the LTC testnet client.

My client has a balance of 0.4 LTC and I sent 0.1 LTC to another wallet address.

https://chain.so/tx/LTCTEST/cc7d6e5e488593fded214e3073195fbaca3807a27d18a7f2550b6fc4909c48f6

Why is the value of the input 0.19 instead of 0.1? Why is this type of transaction created?

Why can't a transaction just be created with 0.1 input and 0.1 output without any change returned?

Thanks in advance.

https://ift.tt/2vK6gVI

Comments

Post a Comment

Popular posts from this blog

Bitcoin Core errors with database block

Bitcoin Core errors with database block I've had the follow issue: on one machine I've launced Bitcoin Core v0.16.0 and Litecoin Core v0.16.0. Each application work in separate datadir also each application have setted callback call for event walletnotify . For now I use both application with testnets. Recently, there have been frequent cases when these applications stop sending transactions, when restarting, an error occurs: "Corrupted block database detected. Do you whant to rebuild the block database now ?". It happens on both apps Bitcoin Core and Litecoin Core, after rebuild applications continue to work, but after a while it happens again Please help me, what I doing wrong? Thank you for any advice https://ift.tt/2z6j9rL
Read more

sendrawtransaction and txn-mempool-conflict

sendrawtransaction and txn-mempool-conflict When i sendrawtransaction to bitcoind, i get error (exceptions) 18: txn-mempool-conflict (use Bitcoin JSON-RPC denpamusic/php-bitcoinrpc ) But the transaction is sent to the network and is subsequently confirmed. Example one decoded transaction : https://jsfiddle.net/rn58a4j6/ then i send this transaction: 94ec12fc463230b4285a29b047608627c05572a4c6eabe6688a201ce49ae72f7 https://ift.tt/2MY2KP0
Read more