In case you have an interest as to the reason for this downside, I imagine this is because of a ‘bug’ (of kinds) within the pockets you have been utilizing, by which the pockets software program would not verify to ensure it isn’t producing mud outputs.
As an instance you have got a single 1.0 BTC UTXO (unspent transaction output) which is on the market for spending, and also you wish to ship 0.99989999 BTC (barely lower than 1.0 BTC – default charge 0.0001 BTC). Then on this case, if that’s the solely UTXO that you’ve, then you definitely can’t truly ship the precise quantity you requested and count on it to get confirmed in time.
0.99989999 (Quantity despatched)
/
1.0 - 0.00000001 (Change)
0.0001 (Miner charge)
It’s best to have the ability to do that, since you have got sufficient to fund the quantity and pay for the charge, however the issue is that the transaction may also normally make a mud output (an output of lower than 5460 satoshis). One resolution is to only mechanically give the additional mud to the individual you might be sending to. One other is to offer it to the miners (by not claiming it in any of the outputs). A greater resolution is to make use of one other UTXO that you simply personal and have the ability to make a refund UTXO which isn’t mud, however this isn’t all the time attainable.
In all of those options, no mud outputs are created. But when the pockets software program simply makes the transaction the same old manner and provides the leftover change again to your self with out checking to be sure that it isn’t mud, then what you noticed occurs and your transaction will not be mined after which is finally thrown out when it turns into sufficiently old.
It is fairly unlikely that this bug would even be obvious in a selected transaction (a few 1 in 18,315 probability), however clearly not unattainable, because you had this downside! Most likely blockchain.information will apply the repair if sufficient individuals complain about it.