Topic: Unconfirmed Bitcoin Transactions for 48 hours already!!! (Read 379 times)
Transactions take longer than they should when the market gets slightly bullish as so many people are making transactions almost every second. The best thing to do is to increase your transaction fee when making payment using any crypto wallet. I set my transaction to priority anytime i am making a bitcoin transaction.
Transaction fees are now only 2 satoshis per byte: https://btc.com/stats/unconfirmed-tx
My transaction got confirmed today finally after waiting 3 days.
My transaction got confirmed today finally after waiting 3 days.
Good that it has been confirmed. This is what you may want to try out should you get sucked in this scenario in the future: you can try to send say $0.5 to the same wallet that is unconfirmed using a higher fee, you may want to use between $2-$3 to send the $0.5 from the same wallet to the previous receiver's wallet or you can do the same stated above transaction to even another wallet. I have noticed that the transaction does get confirmed some minutes or hours after the second transaction might have been confirmed. In the case your transaction fee is up to 0.0001btc, you can use the free accelerator offered by viabtc .com at 00.00hrs.
Something like this happens sometimes , once my transaction which was supposed to be completed in like 2 hours took 2 long days , and I also mailed the concerned authorities and they told me how they are really sorry that the server was down.
Sometimes the receiving wallet and the sending wallet might actually be dealing with a bit of a personal problem which could actually cause a bit of distress for the users.
I am actually happy it got confirmed , what problem and distress it might have caused you we all can understand it happens sometimes .
Good luck for the future ones.
Sometimes the receiving wallet and the sending wallet might actually be dealing with a bit of a personal problem which could actually cause a bit of distress for the users.
I am actually happy it got confirmed , what problem and distress it might have caused you we all can understand it happens sometimes .
Good luck for the future ones.
Because the transaction fee is very low it is not priorty so you wait more than 2 days before the transaction must be complete.
If you set the transaction fee high it less than an hour you will going to use your bitcoin.
That case is normal because once the bitcoin is very high because the miner priotize is high fee than the low fee.
If you set the transaction fee high it less than an hour you will going to use your bitcoin.
That case is normal because once the bitcoin is very high because the miner priotize is high fee than the low fee.
I sent Bitcoin transactions two days ago, nearly 48 hours ago. So far they still show as "Unconfirmed transaction". I set the fee as 8 satoshis per byte, with the total cost to be 0.0000081 BTC. According to this site https://bitcoinfees.earn.com it should take between 25 mins to 480 minutes (8 hours) to be confirmed at 8 satoshis per byte. From their graph there's 2,433 transactions in the last 24 hours with that same fee. What to do and why hasn't it been confirmed yet?
maybe you have to be patient to wait, I know bitcoin is probably currently busy like a crowded vehicle everywhere or maybe now there are improvements so think positively and stay calm 
I sent Bitcoin transactions two days ago, nearly 48 hours ago. So far they still show as "Unconfirmed transaction". I set the fee as 8 satoshis per byte, with the total cost to be 0.0000081 BTC. According to this site https://bitcoinfees.earn.com it should take between 25 mins to 480 minutes (8 hours) to be confirmed at 8 satoshis per byte. From their graph there's 2,433 transactions in the last 24 hours with that same fee. What to do and why hasn't it been confirmed yet?
This happens every time the bitcoin price increases too fast.Why are you so pissed off,the transaction will eventually get confirmed.There's no need hurry.
The confirmation time+transaction speed will normalize,as the bitcoin price is in the "correction" phase.
Transaction fees are now only 2 satoshis per byte: https://btc.com/stats/unconfirmed-tx
My transaction got confirmed today finally after waiting 3 days.
My transaction got confirmed today finally after waiting 3 days.
I sent the coins from my Blockchain.com wallet and unfortunately they set the default fee too low (2.2 Sat/Byte). Now I don't have enough coins to make another payment and need to wait until the transaction is send back.
Another story of blockchain problem when it comes to fees. I still can't believe how they could do it sometimes. They should fix how they decide the fees or there could be more problems and stuck tx from blockchain when the mempool got busy af.
Consider yourselves lucky. I have one transaction pending ever since 25th June and I am really stuck now. Can't cancel the transaction and I have to wait until the pools decides to send the coins back to the originating wallet. And that can take many weeks. I sent the coins from my Blockchain.com wallet and unfortunately they set the default fee too low (2.2 Sat/Byte). Now I don't have enough coins to make another payment and need to wait until the transaction is send back.
I sent Bitcoin transactions two days ago, nearly 48 hours ago.
~
What to do and why hasn't it been confirmed yet?
if your transaction was RBF opted-in, then you can increase its fee higher than current minimum network fee rate ~
What to do and why hasn't it been confirmed yet?
if it wasn't opted-in but has change amount back to your wallet, then you can do CPFP
other than those conditions, just sit back and wait until it gets confirmed
you may want to check your transaction's priority in mempool node on blockchair.com
if it's below ~2000 it should be confirmed in the next block found by a miner
i had the same situation also before that it got stuck because the exchange allotted small tx fee. it took about a week before it got confirmation. i thought i will not get my money anymore.
he's running about 2 days now with this transaction. what he can do is access all the free btc transaction accelerator he knows of and try to enter his tx hash, might help in pushing the confirmation of his tx. and yes, he can always check his tx's priority in the mempool. you will know basically if your tx will be confirmed in the next few days or so.
The network was very busy today, maybe tomorrow when you wake up it'll be already there!!
I sent Bitcoin transactions two days ago, nearly 48 hours ago.
~
What to do and why hasn't it been confirmed yet?
if your transaction was RBF opted-in, then you can increase its fee higher than current minimum network fee rate ~
What to do and why hasn't it been confirmed yet?
if it wasn't opted-in but has change amount back to your wallet, then you can do CPFP
other than those conditions, just sit back and wait until it gets confirmed
you may want to check your transaction's priority in mempool node on blockchair.com
if it's below ~2000 it should be confirmed in the next block found by a miner
You just got unlucky!
Really really unlucky!!
You've sent your transaction when the mempool was quite empty and normally the tx would be accepted but just then a wave of transactions hit the chain, see the red circle.
~snip
Are those transactions will get confirm or will be back to every wallet of the sender? Like the transaction will fail since the transaction fees are too low. Is something like that? or they will wait until the transaction fees will drop around 1-6 satoshi per byte?
. I guess it was because the hype was over then, and the fees dropped. Back then we also tried some of the existing methods of trying to draw the attention of the miners to the transaction, but it didn't really work. 
You just got unlucky!
Really really unlucky!!
You've sent your transaction when the mempool was quite empty and normally the tx would be accepted but just then a wave of transactions hit the chain, see the red circle.
~snip
Are those transactions will get confirm or will be back to every wallet of the sender? Like the transaction will fail since the transaction fees are too low. Is something like that? or they will wait until the transaction fees will drop around 1-6 satoshi per byte?
I don't think your transaction will ever come back again, you just have to be patient in the future to wait for confirmation to finish. It might be long enough for your transaction to be confirmed but try to be patient, I'm sure it must be confirmed.
Thanks for the graph, I want to ask some questions about what will happen those unconfirmed transactions around 1-6 satoshi/byte or more than that area, that is still unconfirmed?
Are those transactions will get confirm or will be back to every wallet of the sender? Like the transaction will fail since the transaction fees are too low. Is something like that? or they will wait until the transaction fees will drop around 1-6 satoshi per byte?
Are those transactions will get confirm or will be back to every wallet of the sender? Like the transaction will fail since the transaction fees are too low. Is something like that? or they will wait until the transaction fees will drop around 1-6 satoshi per byte?
Well, the answer is in the wall of text above from DannyHamilton that dothebeats quoted:
Transactions never get "kicked back out". Some nodes, miners, and mining pools may choose to forget the transaction after a while if it hasn't confirmed yet, but if you store the raw transaction somewhere you can always re-broadcast it yourself to remind them until it finally confirms.
The longest period of time a tx was kept in the mempools that I know about was 27 days before it was confirmed.
Don't know if the user continued to rebroadcast the tx or not but any tx should manage to stay at least the same time.
But the weekend is coming, prices are not spiking anymore, and miners are either adding gear or having luck (we're 4 blocks ahead of schedule) so it should get confirmed.
You just got unlucky!
Really really unlucky!!
You've sent your transaction when the mempool was quite empty and normally the tx would be accepted but just then a wave of transactions hit the chain, see the red circle.
~snip
Are those transactions will get confirm or will be back to every wallet of the sender? Like the transaction will fail since the transaction fees are too low. Is something like that? or they will wait until the transaction fees will drop around 1-6 satoshi per byte?
Under normal circumstances, there is no chance of any transaction returning. But there are examples of rollbacks applied before. The transactions will be completed after a certain period of time.
You just got unlucky!
Really really unlucky!!
You've sent your transaction when the mempool was quite empty and normally the tx would be accepted but just then a wave of transactions hit the chain, see the red circle.
~snip
Are those transactions will get confirm or will be back to every wallet of the sender? Like the transaction will fail since the transaction fees are too low. Is something like that? or they will wait until the transaction fees will drop around 1-6 satoshi per byte?
I sent Bitcoin transactions two days ago, nearly 48 hours ago. So far they still show as "Unconfirmed transaction". I set the fee as 8 satoshis per byte, with the total cost to be 0.0000081 BTC. According to this site https://bitcoinfees.earn.com it should take between 25 mins to 480 minutes (8 hours) to be confirmed at 8 satoshis per byte. From their graph there's 2,433 transactions in the last 24 hours with that same fee. What to do and why hasn't it been confirmed yet?
When the Bitcoin price moves at this rate, the number of transactions increases rapidly. And the validation of transactions is starting to delay. As this mobility continues, the sequence increases.
In addition, especially in such cases, transactions over the exchange can take longer. Where did you start the BTC transfer in question? From your personal BTC wallet?
legendary
Activity: 2464
Merit: 3878
Hire Bitcointalk Camp. Manager @ r7promotions.com
You just got unlucky!
Really really unlucky!!
Really really unlucky!!
Twice unlucky.
The recommended fee has dropped less than 1h ago to 12 satoshi/byte and 1-2 new blocks would have probably gotten his transaction.
Now another wave is on and the recommended fee is 122 sat/byte.
I wanted to send the BTC in an exchange and when I saw the regular fee goes over $4 I thought fu*k it. So I edited it to 20 Sat/Byte leaving it to my luck.
Anyway, I would suggest OP just to wait unless you have urgency for this tx.
You just got unlucky!
Really really unlucky!!
Really really unlucky!!
Twice unlucky.
The recommended fee has dropped less than 1h ago to 12 satoshi/byte and 1-2 new blocks would have probably gotten his transaction.
Now another wave is on and the recommended fee is 122 sat/byte.
Now I hope you guys jinx it. The new wave of transaction doesn't seem to be coming down or lying low for the next few hours. Mempool seems to be pretty much adding up new transactions faster than miners can clear it. Well at this rate, OP would just want to hope for the best and wish that some miners out there would include his transaction, though I doubt it knowing that his tx is already deep within the mempool already. Just like what stompix said, a CPFP tx would do the trick.
Or try what DannyHamilton stated here (warning: huge block of text):
I've been trying to use the accelerator but am continually getting the message "Submissions are beyond limit. Please try later."
The accelerator only allows 100 free accelerations per hour. They reset at the beginning of the hour. This means you need to attempt your acceleration withing the first minute or so of the hour. After that 100 other people will have already used up the 100 slots.
In case your clock isn't set identically to theirs, I'd suggest trying at about 2 minutes before the beginning of the hour, and then re-trying every 15 seconds or so until a few minutes after the beginning of the hour. You should succeed during one of those attempts.
since this transaction was a BTC purchase through the Glidera exchange, does anyone know what would happen if the transaction does not get confirmed and gets kicked back out?
Transactions never get "kicked back out". Some nodes, miners, and mining pools may choose to forget the transaction after a while if it hasn't confirmed yet, but if you store the raw transaction somewhere you can always re-broadcast it yourself to remind them until it finally confirms. If you don't do that, then you'll have to contact Glidera to find out what they do about unconfirmed transactions. Perhaps they'll re-broadcast. Perhaps they'll send a new transaction. Perhaps they'll steal your money and tell you "tough luck". I can't predict what someone else will do.
1. With CPFP, do I need to spend ALL of the unconfirmed funds, or just make sure that SOME of the uncomforted funds are being used?
You just need to use the unconfirmed transaction output as an input to the fee paying transaction. How much of that input you send elsewhere and how much you just send to a different address in your same wallet is entirely up to you.
2. I understand that I need to make sure a high enough fee is being paid to cover both transactions, but do I also factor in the .0003164 BTC on the unconfirmed transaction as part of the total amount when considering how much more to send ? In other words, if I wanted to make sure the fee on each transaction was .0004164 BTC, would I send 2x this amount, or would I send .0004164 BTC for the child transaction plus an additional 0.0001 BTC for the parent transaction (since .0003164 is already included in the original transaction)?
Generally miners that implement CPFP properly would add up the total bytes from both transactions and the total fees from both transactions. Then they'd calculate the fees paid per byte and compare to the fees per byte of all the other transactions (both other CPFP and other non-CPFP). The transaction (or set of transactions) that get the miner the highest profit (most fees per byte) would then get confirmed.
If you decide later that you need to re-broadcast the transaction, here is the raw transaction:
Code:
0100000001dc2736bf4834fec9d7f5fc8930f34402a264f0a2f73e67c49a4099d75f16db6b010000006b483045022100b55d29a8e5e514a3636bfd072a986fde1014a45ad3e99164bdde363190d853fd0220576dfdf5d49efdc8cc30e72a2a8abe1a7498b648ac455d8605acc23cbcb22ed10121025834c58e5c1aae14e66a669e4b342a1e498258d0a6a5013f86c6535f2ac2e42affffffff0248e4d200000000001976a914cf41ac8d5d0cd15470cb64aa426bad1436bb2f2388acf0d2fe01000000001976a9148968a3751be6bf8446cbf93623a00968b21e187d88ac00000000
https://blockchain.info/rawtx/8f46d46df82a4200e86e485653d725eab567043bbb008688aff964ab26db6197?format=hex
Jump to: