Q about a transaction

[lilSpender]

Hello forum,

someone is a complete newbee to bitcoins, so i have a question about a transaction.
If this is posted in the wrong forum, sorry about that. Than please, mod? Relocate this to the appropriate section.

The problem:

yesterday someone send two dollar something with a bit of fee to an address. Within 20 minutes it was confirmed and done.
Now 20 minutes later someone send 0.086774 BTC
from: 1FG5PHYrYxogPFs53TTRDcUWGWr1JguRDW
to: 1LMojUUSRgz1NNZ2kiZgsc8pb39RgvDJsy
With again a little fee: 0.0002 BTC

But it has zero confirmation for more than 24 hours, bordering 30 hours.
And i have no idea what could be the problem.

Maybe someone can have a look here:
https://blockchain.info/nl/address/1LMojUUSRgz1NNZ2kiZgsc8pb39RgvDJsy

and explain to me what is wrong, if anything?
That would be much appreciated.

With regards,

LS.

[jacee]

Hello forum,

someone is a complete newbee to bitcoins, so i have a question about a transaction.
If this is posted in the wrong forum, sorry about that. Than please, mod? Relocate this to the appropriate section.

The problem:

yesterday someone send two dollar something with a bit of fee to an address. Within 20 minutes it was confirmed and done.
Now 20 minutes later someone send 0.086774 BTC
from: 1FG5PHYrYxogPFs53TTRDcUWGWr1JguRDW
to: 1LMojUUSRgz1NNZ2kiZgsc8pb39RgvDJsy
With again a little fee: 0.0002 BTC

But it has zero confirmation for more than 24 hours, bordering 30 hours.
And i have no idea what could be the problem.

Maybe someone can have a look here:
https://blockchain.info/nl/address/1LMojUUSRgz1NNZ2kiZgsc8pb39RgvDJsy

and explain to me what is wrong, if anything?
That would be much appreciated.

With regards,

LS.

Must be a malleability attack. Do you know where the bitcoin came from or who sent it to you?

[shorena]

1st: welcome.

This is the transaction we talk about -> https://blockchain.info/tx/4a3ea868169eae2a00007c7f588c87e2ca9cfcb69cd40ec34f0a5c872ff98ab6?show_adv=true

Its small 257 byte and pays a high fee 0.0002, but one of the outputs is considered "dust".

You use a 0.08697448 BTC input to send 0.086774 BTC with a 0.0002 fee that leaves

0.086 974 48 - 0.086 774 - 0.000 2 = 0.000 000 48 BTC change. This change is what causes the hold up. Because its so small most nodes will not relay your transaction, thus it has a hard time to reach miners.

Currently dust is considered 2730 satoshi or less.

Miners can and will confirm the transaction, it might just take longer than usual. Whoever send that TX needs to keep this in mind in the future. If the sender is unable to influence this the wallet used needs a fix.

[lilSpender]

Hi and thanks for the reply.

Must be a malleability attack. Do you know where the bitcoin came from or who sent it to you?

Yes i do. The sender is the same person as the receiver. So there was absolutely no malicous intend.

0.086 974 48 - 0.086 774 - 0.000 2 = 0.000 000 48 BTC change. This change is what causes the hold up.

This is weird, because the 48 satoshi were never send with this TX?

Anyway,

what i can take back from this is: be patient and let it ride.
It will come through eventually?

Is this correct? It would very much ease someone's worries.

Cheers!

EDIT: the sender will keep in mind that "dust" should never get broadcasted to the network!

[shorena]

Hi and thanks for the reply.

Must be a malleability attack. Do you know where the bitcoin came from or who sent it to you?

Yes i do. The sender is the same person as the receiver. So there was absolutely no malicous intend.

0.086 974 48 - 0.086 774 - 0.000 2 = 0.000 000 48 BTC change. This change is what causes the hold up.

This is weird, because the 48 satoshi were never send with this TX?

Well you have to use the input (0.086...) entirely. If your wallet or service does not add dust to the fee it will send it to an address you control.

You have no balance in bitcoin, think of it like having a 0.086 974 48 BTC bill. If you spend it you cant spend it partially.

Anyway,

what i can take back from this is: be patient and let it ride.
It will come through eventually?

Either way, waiting is the only thing you can do now. You either need to wait until the network forgets about the TX and you can send another one or until the TX gets confirmed.

Thus ~48-72 hours max.

Is this correct? It would very much ease someone's worries.

Cheers!

EDIT: the sender will keep in mind that "dust" should never get broadcasted to the network!

[lilSpender]

Ok, that clears things up.

I'll just wait untill it either goes through, or get's dropped / forget by the network.
If it doesn't come through, i resend without "dust".

Thanks a bunch!