stuck transaction

[ilib]

Please take a look at this transaction
https://www.blockchain.com/btc/address/3DgYkeJR7QC6YEsYRawr3KoXvit7N6SWuf

The transaction from an address with confirmed coins and with quite sufficient Tx fee is not confirmed since afternoon till midnight!
What can be the reason of such delay?
I guess CPFP won't help as the parent was confirmed yesterday

Hopefully at the time you read this it will be confirmed already.

[1715343340]

1715343340

[1715343340]

1715343340

[BlackHatCoiner]

Omg. It's 9 hours stuck? The fees aren't bad. I have seen my 10 satoshis per byte confirmed within 5-6 hours. That is strange.

[hosseinimr93]

I guess CPFP won't help as the parent was confirmed yesterday

Seems that you don't know exactly how CPFP works. Both outputs are still unspent.
If you want to accelerate the confirmation using CPFP method, you need to spend the fund from one of outputs of the unconfirmed transaction using a high fee.

Let's say the fund has been sent from address A to address B and then from address B to address C.
In CPFP method, the second transaction helps the first transaction to be confirmed. The first transaction cannot help the second transaction.

If you have control over one of outputs of the transaction, you can use CPFP method.
If you have control over inputs and you are in hurry, since the transaction is RBF, the best thing you can do is to bump the fee.

[ilib]

I guess CPFP won't help as the parent was confirmed yesterday

Seems that you don't know exactly how CPFP works. Both outputs are still unspent.
If you want to accelerate the confirmation using CPFP method, you need to spend the fund from one of outputs of the unconfirmed transaction using a high fee.

Let's say the fund has been sent from address A to address B and then from address B to address C.
In CPFP method, the second transaction helps the first transaction to be confirmed. The first transaction cannot help the second transaction.

If you have control over one of outputs of the transaction, you can use CPFP method.
If you have control over inputs and you are in hurry, since the transaction is RBF, the best thing you can do is to bump the fee.

In Electrum under History tab if I right click on the unconfirmed transaction there is a pulldown menu with an option "Child pays for parent". Then I can set the desired Tx fee. Will this help?

[BitMaxz]

In Electrum under History tab if I right click on the unconfirmed transaction there is a pulldown menu with an option "Child pays for parent". Then I can set the desired Tx fee. Will this help?

Yes, it can help to accelerate your transaction so make sure to increase the fee to cover the parent transaction.

Another thing that I think can accelerate your transaction is to submit the TXID on the ViaBTC accelerator.
The unconfirmed transaction from your address has 0.00010304 fees so you can able to submit it

Here's the accelerator link below.
- https://www.viabtc.com/tools/txaccelerator/

[hosseinimr93]

In Electrum under History tab if I right click on the unconfirmed transaction there is a pulldown menu with an option "Child pays for parent". Then I can set the desired Tx fee. Will this help?

Yes, it will be helpful. Just send the unconfirmed output to another address with a high fee.

Note that the fee should be that high, so miners include both transactions in a single block.

Assuming the unconfirmed transaction is A and the transaction you are going to make is B, the fee (sat/byte) you need to pay for transaction B will be as follows.

f_B = (f*(S_A+S_B) - f_A*S_A) / (S_B)


f is the fee (sat/byte) needed to be paid for a transaction to be included within certain number of blocks.
f_A is the fee (sat/byte) has been paid for transaction A
S_A is the size (byte) of transaction A
S_B is the size (byte) of transaction B

[HCP]

The transaction from an address with confirmed coins and with quite sufficient Tx fee is not confirmed since afternoon till midnight!
What can be the reason of such delay?

The reason?

Fee per byte 46.000 sat/B
Fee per weight unit 11.500 sat/WU

While you paid "46 sat/Byte"... because it's using legacy inputs/outputs... your transaction fee is only 11.5 sats/Weight Unit... and this is what has been happening on the network in recent hours:


Even given the relatively high fee, you're still several blocks worth of transactions from the tip:



Blockchair is calculating your "priority" as 14031...

Once, things settle down, the transaction should confirm... or you can try using RBF ("Replace-by-Fee") to increase the fee as your transaction appears to be RBF-enabled and you are using Electrum.