Quote from: innominatus on November 23, 2016, 05:33:40 PM

Quote from: johny1976 on November 23, 2016, 04:42:23 PM

Quote from: innominatus on November 23, 2016, 04:01:19 PM

Quote from: ranochigo on November 23, 2016, 11:37:03 AM

Both of the transactions have several inputs and the total output amount is less than the input amount so you paid a fee and it satisfy the protocol rules.

However, other than the significantly low fees when compared to the average fee in the mempool, the transaction [1] spends an input[2] that is unconfirmed. Hence, the transaction[2] MUST BE to confirmed first before transaction [1] will confirm. They can be included in the same or different blocks.

[1] d8d6ec17b102812f0d989b469fce1993b22e7ea13a5fa5fa401f27d5d8fdf24f
[2] 5005f2baa7170c13ce5e104c7cd238479b75197b4aa32434963d06fd9625229f

is there a chance that it won't get confirmed as the deal i have paid for is closed.
how can i stop broadcasting that?

I see a "high priority" that is said from some internal Blockchain.info calculation. It will eventualy get confirmed, it may take a bit longer, but it will.

No need to stop broadcasting it.

Mate, you do not read what I wrote.
I do not want it confirmed, because the deal I was paying is not active anymore.
So I do ask again, is there any chance I could stop broadcasting it and get dumped in mempool?

Sorry for my misunderstanding, I think there's no way to achieve that. The transaction will be confirmed.

EDIT

Ok, didn't know about the double-spend. Think it's time for me to leave this conversation Cheesy