What is wrong with this transaction? (not confirming)

[rrdein]

The fee should have been 0.0005/kB, that's the correct number, right?  Can anyone verify Electrum did the math correct?  The person I sent it to said plenty of other people had paid and were confirmed in this time period.  Any thoughts?

https://blockchain.info/tx/d0f672ff289a8317ce2f7f976d5df307ecf680643a35274d37d181f4ff058279

[1714821000]

1714821000

[1714821000]

1714821000

[1714821000]

1714821000

[digaran]

What transaction? all I see is you complaining, you need to provide the txid so we could check it out and tell you what needs to be done.
Give it a few minutes to get second confirmation because I just confirmed it for you.

[Sundark]

The correct and the most efficient fee right now is 120 satoshis per byte of data sent. Without transaction ID we can't help you to detect what is wrong.
If your transaction is stuck in the mempool then your fee most likely was too low.

[rrdein]

Sorry, I fixed my post.

[steven0021]

The fee should have been 0.0005/kB, that's the correct number, right?  Can anyone verify Electrum did the math correct?  The person I sent it to said plenty of other people had paid and were confirmed in this time period.  Any thoughts?

https://blockchain.info/tx/d0f672ff289a8317ce2f7f976d5df307ecf680643a35274d37d181f4ff058279

The math is correct. 12900 (fee)/257 (size) = 50.19 satoshi per byte or 0.0005BTC/KB.
But 50 satoshi per byte is not enough to get a fast confirmation. I've seen a tx with 50 satoshi per byte not confirming since yesterday. The recommended fee is more than double that amount according to https://bitcoinfees.21.co/.

You can use https://www.viabtc.com/tools/txaccelerator/ to make a low fee transaction with at least 0.0001/KB confirm within few hours. I already submitted it but that link might be useful for future uses.

[rrdein]

Thank you so much for the useful information.

[loserkids]

You may also use replace-by-fee to spend the same output again. Next time you make transactions during big backlog make sure to use the feature.

Tools -> Electrum preferences -> Enable Replace-By-Fee

https://i.imgur.com/lEaLoIx.png

Send -> click "Replaceable"

https://i.imgur.com/sIwJc05.png

[rrdein]

Thanks for that.  What is the actual difference (as far as the blockchain is concerned) between a RBF and non-RBF transaction?

[steven0021]

Thanks for that.  What is the actual difference (as far as the blockchain is concerned) between a RBF and non-RBF transaction?

With RBF you can replace an unconfirmed transaction with another identical transaction but with higher fee (the fee will be subtracted from the output) without having to wait for the nodes to drop the conflicting transaction. Non-RBF transactions can't be replaced unless nodes have already dropped the conflicting transaction.

Edit:
Note that not all nodes (and electrum servers) enables RBF. Sometimes your RBF transaction will be rejected even though it is flagged as replaceable. Change servers and try again if that happens.

[loserkids]

Note that not all nodes (and electrum servers) enables RBF. Sometimes your RBF transaction will be rejected even though it is flagged as replaceable. Change servers and try again if that happens.

Is it possible to know which nodes accept RBF other than by trial and error?

[cengsuwuei]

i can see youre problem is solved
without confirmation transaction, but youre balance is receive and send out again
https://blockchain.info/address/  snipe addres is 1CFRRa
if i write complete youre addres can detection in my profile is my addres so iam not complete addres iam anlys your transaction

[Karpeles]

There is a peak of unconfirmed transactions(more than 50k) right now, so there is a big chance that a transaction sent would take several hours until it gets a confirmation, no matter what the transaction fee(there are topics about this if you want to know why and stuff)

Better take into consideration the possibility of the transaction be stuck for some long hours when you send it until things are back to normal

[Kakmakr]

Just as a side note, this is not the norm. We are currently experiencing a "spam" attack and there are about 60 000 transactions in a huge backlog because of this. So do not get discouraged by this, and follow the advice that was given in this thread so far. The problem comes in when you are not the one sending the money and they used some wallet service that do not have the option to increase the fees. ^hmmmmmm^

[hawkins]

lately transactions it feels long, try to wait a while longer. maybe it will take place in a few minutes, or hours, but I believe, that transaction must have run immediately. I also never experienced anything like this, but after a few hours, I have been in the confirmation transaction.

[Windpower]

The fee should have been 0.0005/kB, that's the correct number, right?  Can anyone verify Electrum did the math correct?  The person I sent it to said plenty of other people had paid and were confirmed in this time period.  Any thoughts?

https://blockchain.info/tx/d0f672ff289a8317ce2f7f976d5df307ecf680643a35274d37d181f4ff058279

I have been waiting for a couple of hours now for a transaction where I used 0.0001/kb. You have gotten some great information from the other people on this forum that you should definitely use. I will also try to use some of them with my future transactions. I definitely think you should use a higher fee in the future if you want your transaction to be confirmed quickly. I guess now it is just a waiting game for you.

[Sundark]

lately transactions it feels long, try to wait a while longer. maybe it will take place in a few minutes, or hours, but I believe, that transaction must have run immediately. I also never experienced anything like this, but after a few hours, I have been in the confirmation transaction.

It is all because you probably didn't adjust your fee accordingly. If you pay current standard 120 satoshi per byte your transaction will be confirmed very quickly.
There is no really any magic behind that other that miners are becoming more greedy.