This ones really got me stumped

[WTFTX]

https://blockchair.com/bitcoin/transaction/20d5617e7e90cb5a5de25b272c04dc46806549048d281c5cd444b31db751c1d5

Any ideas on what's going on here?

Sent high fee a day ago. Been a the top of the queue, never gets confirmed.

Thanks for any insight.

[jackg]

Afaik that's 2000+ sats/byte and a smallish transaction and recommended fees are around 300 sats per byte so I'm not sure what's happening with it... There's a possibility a bunch of miners have blacklisted it or sonething but I'm not sure how likely that is, maybe it's just unlucky....

[WTFTX]

Afaik that's 2000+ sats/byte and a smallish transaction and recommended fees are around 300 sats per byte so I'm not sure what's happening with it... There's a possibility a bunch of miners have blacklisted it or sonething but I'm not sure how likely that is, maybe it's just unlucky....

Is there any way I could be put in contact with a miner that would manually confirm this? It's quite a large transaction and I'm starting to get worried

[jackg]

Only one I can think of is macbook-air they haven't been online here for a while but if they still own F2pool and gets a notification of the pm they might be able to help.

[BitMaxz]

Such a big fee but it still stuck? It should be confirmed fast since you paid a high fee.

It seems a series of unconfirmed transactions.

This transaction https://blockchair.com/bitcoin/transaction/93034a0b165482f8d0725f51b51da1b7186561807cdc263092f48af08a1f44bf

Is where your BTC from before your new transaction which is still not confirmed but the fee should be enough to confirm in a few hours.

Do you have control of these addresses below?

Code:

1QByDb2yWiCAWLBKaJoa8yEoomDbLJeWEQ
19uxgZXZMVRqdqxFxPXJfr4NTnerpaVaYi

If you have full control of these addresses you can still make a double-spend transaction.

If not, try to push that transaction first use the free accelerator from here https://www.viabtc.com/tools/txaccelerator/

Ow, it seems this address 1QByDb2yWiCAWLBKaJoa8yEoomDbLJeWEQ is the reason why your transaction still stuck, it has some transaction with very low fee and most of inputs are unconfirm yet.

[seoincorporation]

The problem it that some of the inputs in the transaction still unconfirmed, you need a chain of confirmations now. Your transaction will not confirm until these transactions confirm.

https://www.blockchain.com/btc/tx/ba16ebd3771594279b1451f3386934f1cf5b35310243c534b5a0c5961c413860
https://www.blockchain.com/es/btc/tx/0fecb924aa5e62a0298c57dde5bfa3fc8bab17ec07ef30c674b33337d42b33b1

Miners can't confirm transactions who have unconfirmed inputs, this is because those inputs could be double spent. So, is about time and patience, your transaction will confirm if the input doesn't get double spent.

[o_e_l_e_o]

Miners can't confirm transactions who have unconfirmed inputs, this is because those inputs could be double spent.

This isn't accurate. Miners can quite happily confirm a transaction with unconfirmed inputs, provided that they also confirm all the inputs at the same time. This is the basis for "Child Pays For Parent" transactions - a child with a much higher fee rate than its unconfirmed parent which means when you consider both transactions together the overall fee rate is higher than the parent fee rate alone.

OPs transaction could be confirmed if the miners also choose to confirm all the parents at the same time. The issue here is that there is a chain of multiple unconfirmed parents, all paying a very low fee rate, and some of significant size - one of 4,300 vbytes and another of over 8,000 vbytes. If you add up all the sizes and use that number to divide the total fee, then the effective fee rate for all these transactions together is far lower than the 2,000 sats/vbyte fee OP has paid on the final transaction in the chain.

[favebook]

I am not sure how you managed to get your transaction stuck with such a high fee, but it has been sent and confirmed 4 times as of 29 minutes ago since I posted this.

[nc50lc]

-snip- then the effective fee rate for all these transactions together is far lower than the 2,000 sats/vbyte fee OP has paid on the final transaction in the chain.

That's actually what happened, the consolidated fee rate of the transaction's parent-child chain is 90sat/vB  

I'm surprised that it even got mined during this time when "1mb-from-tip" didn't even reached below 100sat/vB.
Looks like spider's accelerator is legit, OP had requested to include his txn and the parent txns (previous posts of the quote) to the accelerator:

And the big Tx:

20d5617e7e90cb5a5de25b272c04dc46806549048d281c5cd444b31db751c1d5

done

[hulla]

-snip- then the effective fee rate for all these transactions together is far lower than the 2,000 sats/vbyte fee OP has paid on the final transaction in the chain.

That's actually what happened, the consolidated fee rate of the transaction's parent-child chain is 90sat/vB  

I'm surprised that it even got mined during this time when "1mb-from-tip" didn't even reached below 100sat/vB.
Looks like spider's accelerator is legit, OP had requested to include his txn and the parent txns (previous posts of the quote) to the accelerator:

Maybe not the last time I checked all free tx acceleration I know are done through the rebroadcast of the transaction and a lot of stuck transactions with low tx fees seem to be confirmed yesterday but for the OP I think accelerating the parent transaction helps the situation.

[nc50lc]

-snip-

Maybe not the last time I checked all free tx acceleration I know are done through the rebroadcast of the transaction

Most of those users with "re-broadcast" accelerator service thread were already tagged for "scam due to misleading service".
That one survives, but there're still too few variables to consider it as 100% legit
(Update: he could be another "re-broadcast accelerator" since his "done" quotes of confirmed txns were mostly mined by random pools).
For the transactions, it was confirmed together with the parent because a miner cannot include the child without including the unconfirmed parent, obviously.

FYI, the average fee rate during that time was much higher the the consolidated fee rate of the OP's txn chain.
So it can't be confirmed "normally" at the time when it was confirmed.

and a lot of stuck transactions with low tx fees seem to be confirmed yesterday but for the OP I think accelerating the parent transaction helps the situation.

Is that a guess? Because mempools' sizes didn't seem to get any lower since yesterday.