A way to solve unconfirmed tx (tested w/blockchain.info only 1 time)

[kxp]

Perhaps I am not by far the first one who discovered this, but the thing is I had an unconfirmed tx for a while (like a week). I gave up on it and moved on (the tx was low amount), the reason for it being stuck was actually a low fee (my error when setting it).
Today I had to pay for another thing (different receiving address) and I did it from same wallet (address) and set a higher fee (265 s/b). Tx got confirmed, but to my surprise the prev tx got confirmed as well (after a week of hanging) and now both of them have same number of confirmation.
Likely the new tx, though being sent to different address, somehow promoted the first one which had a low fee. Ofc one case doesn't mean it shall work any time (and I don't wanna experiment much, better set competitive fees) but if you got some important tx stuck and amount is considerable I'd try and buy smth cheap but with higher fee from same wallet or send to another wallet of mine.

[1713442702]

1713442702

[Patinix]

Haven't thought of this before 

Good tip! (if it works)

[icerose]

Its a well known fact u can push an original transaction by setting a high fee on subsequent transactions, after all miners want to earn as much as possible. Most wallets however don't allow you to spend unconfirmed transactions so you need to use one that does allow you to.

[PokerFace3]

I do see it as just a coincident.
AFAIK, when miners do find new transactions for their new block, they will not mind about what were the previous transactions which are pertaining to sending/receiving addresses. They will pick up the transactions which are having tx fees included up to their expectation levels.

Could you share your bitcoin address into which the situation you have explained happened. That may help people here to understand your method better and also to try your method so that we may get a concrete conclusions.

[kxp]

I do see it as just a coincident.

Ok everything could be but I don't believe that.

Tx1: https://blockchain.info/tx/c5e1289c0ea6b8848a93a4fb3e9117d786ef17c5561ca8cbf2e2f26d57bd1a4d
Tx2: https://blockchain.info/tx/47c3b5a501ee4a7e9d7a158a2fcb9ee75da9e9744e0fe4b8783354fb97d18492

Note same number of confirmations.

I don't know if it is possible to see when tx started to confirm, but I remember the first being unconfirmed when I was sending the second (today) and when I checked after about an hour both got confirmed.

[BrewMaster]

i would have said this was a case of CPFP but the fees don't really add up.

how CPFP (Child Pays For Parent) works is that you spend an unconfirmed transaction (like what you did with your second tx) but pay a higher fee so that it can cover both transactions.

transaction fee has been more than 300 satoshi per byte for the past week. so the first transaction needed 200 s/b additional fee in total of 51000 and second transaction needed an additional 40 s/b total of 1024 satoshi so you in fact paid less fees required for a CPFP so both of your transactions had a pretty low priority to be confirmed, in other words it looks to me more like you got lucky

[kxp]

transaction fee has been more than 300 satoshi per byte for the past week. so the first transaction needed 200 s/b additional fee in total of 51000 and second transaction needed an additional 40 s/b total of 1024 satoshi so you in fact paid less fees required for a CPFP so both of your transactions had a pretty low priority to be confirmed, in other words it looks to me more like you got lucky

Lol are you kidding?
The tx was stuck for 5 days and got confirmed same hour as second one was submitted. Well everything could be but you have to admit this has really a very low probability.
Also doesn't CPFP have to be sent to the same address as the first tx?

[Iranus]

transaction fee has been more than 300 satoshi per byte for the past week. so the first transaction needed 200 s/b additional fee in total of 51000 and second transaction needed an additional 40 s/b total of 1024 satoshi so you in fact paid less fees required for a CPFP so both of your transactions had a pretty low priority to be confirmed, in other words it looks to me more like you got lucky

Lol are you kidding?
The tx was stuck for 5 days and got confirmed same hour as second one was submitted. Well everything could be but you have to admit this has really a very low probability.

Several Bitcoin transactions are sent every second.  The probability of it happening to at least one person is nearly 100%, and that's the same with several other possible coincidences. 

[BrewMaster]

transaction fee has been more than 300 satoshi per byte for the past week. so the first transaction needed 200 s/b additional fee in total of 51000 and second transaction needed an additional 40 s/b total of 1024 satoshi so you in fact paid less fees required for a CPFP so both of your transactions had a pretty low priority to be confirmed, in other words it looks to me more like you got lucky

Lol are you kidding?
The tx was stuck for 5 days and got confirmed same hour as second one was submitted. Well everything could be but you have to admit this has really a very low probability.
Also doesn't CPFP have to be sent to the same address as the first tx?

no i am serious
these are all guesses though, because the only way to know for 100% sure is to have the mempool of the time of your transaction and analyze the transactions to see how many were with higher priority than you. it is possible that there weren't enough transactions with higher priority (or higher fee than 106 s/b) so your turn was up.

i had 2 transactions with 180 s/b and they got both confirmed yesterday!

and for CPFP you spend outputs.
your first transaction created an output called c5e1289c0e..... and to perform a CPFP you should have spent this output which you accidentally did and created a new one called 47c3b5a501.... . it doesn't matter where you send these to.