Bitcoin Forum

I made transactions from blockchain to other bitcoin address. Its been 22 days.. For 2-3 weeks it was pending now its showing removed/DoubleSpending. Please can anyone help me getting my funds back

Txn id
6f991677bdbd929019f54bcd442c0930ca0e1987c16907eef9e2c256e11a7611

https://btc.com/6f991677bdbd929019f54bcd442c0930ca0e1987c16907eef9e2c256e11a7611 (https://btc.com/6f991677bdbd929019f54bcd442c0930ca0e1987c16907eef9e2c256e11a7611)

Thank u :)

Please can anyone help :)

Try pool.viabtc.com/tools/txaccelerator to accelerate your transaction and load the transaction on to the site at the closest time to the hour as you can.

Else, look in the services section here for free transaction accelerators (or ones that are paid for if you're desperite).

Sir i guess they confirm transactions with fees more then 0.001 btc plus mine is now removed/ DoubleSpending

its also happened to me, i'm really confuse how to get my bitcoins back into my wallet. Even the support is not answer my ticket

Can you export your private keys from blockchain.info and import them to Electrum?

They didn't last time I used them.
They want 10sats/byte but I'm not sure they validate that yet - last time I checked. I'm sure I loaded a transaction at about 5sats/byte into them once. They do validate it now... :(

Look in the services section here also for FREE services that will accelerate them in a few hours.

https://bitcointalk.org/index.php?board=52.0 - Link to the services section here.

I wanted to understand is their any way where we can cancel the transaction . As mine is also struck from 1 week. In case say if we cannot cancel manually then in how many days will it get automatically cancel? Is their any specified days like if it dint went through then it automatically gets cancelled?

There is nothing that cancels it.

You can try getting the private key ans sweeping it into another wallet, as that will go down as a double spend to may not be propagated as well → although, providing the transaction fee per byte is higher, it should go through and knock the other transaction out of the mempool and replace it.

Transactions are supposed to expire from the mempool after 21 days of them being made. However, as it is a decentralized currency, everyone can set a different rule on their node and keep the transaction being broadcast into the mempool.

2 problems I see on your transaction: low tx fee (5 sat/B) and dust output (575 sats)
most nodes probably auto reject your tx, I don't understand why bc.info let you create such tx output (dust)
and the low tx fee puts your tx queued with very low priority in the mempool
one easy way you can do is by exporting and importing privkeys to other wallet

This is a lesson on the importance of paying the right fees. Pay almost nothing and you wait forever. Pay the correct fee (yes, it might be expensive) and you are given the red carpet treatment.

As mentioned by others, you should try free accelerators or search for someone here who might know someone from a mining pool who can confirm your transaction for a fee. A lot of "who" there. When you need something done, it's all about knowing someone with friends of friends of those you need help from. To avoid all the drama and confusion, pay the right fees.

22 days. That's a long wait. Wait longer and you will have a whole month to talk about. The perfect ice breaker topic to end any dinner party awkwardness.

Sorry to see you in this predicament. On the bright side, bitcoin seems to be regaining strong ground again. Better than 22 days ago at 12k per coin. If you see your coins confirmed today or before the end of the year, this should be something to be happy about.

Try a TX accelerator maybe? Did you send from an exchange or wallet? Fee seems really low

I sent it through blockchain.. I didn't intentionally send low fee.. It was blockchains default fee

Going forward kindly convert your btc to ETH or some other coin and send the transfer so that easily it can reach the recipient and confirmation will take place quickly. Also their network fees is very low. I had also faced this issue before and waited for a week or so and finally it got confirmed after the the acceleration was done.

Tx : 82623b0cbef02a516969abc7301ec5b1b753d1f0744151d58457ef6a1d09bd2d

Pool want more btc for acceleration  :'( i don' t have now
Solution?

This is why a lot of people I know left with their money and went back to stock trading or trading alt coins. 22 days and still no confirmations? That's just too much

If you close your wallet and wait a few days, the transaction will be dropped from the network and BTC will return to your wallet. After that you can make a new transaction with appropriate fees.

(It is important to NOT launch your wallet because your wallet will keep re-broadcasting the transaction to network and it will never get dropped or confirmed. It will be stuck in limbo forever)

Bro i sent it from my blockchain wallet.. So by ur suggestion i shd log out from wallet n log in after few days?? Is it wat u sayin

good luck

I've had a transaction stuck since 10-29-17. That shows as still in mempool .
I had another transaction I was able to abandon and it came back to me.
I've had my wallet closed for a few days and nothing has happened to it. I guess I need to wait a few weeks and not open it.
Which is just plain silly...

Any techno greek can help me

Rajput69 i can try. Today i have confirmed my old transaction

Previous Person is Scamer. I added your tx in free acceleration .

Plz do

by any chance you want to try the harder way?
exporting your private keys off bc.info wallet and importing them to other wallet (or use tools)
followed by making double spend tx attempt with higher tx fee

In that case I don't have any idea, I've never used that online wallet.

I use Electrum which has a very useful feature "Replace by fee". It gives you a chance to broadcast a stuck transaction with higher fees. Highly recommended. I would suggest getting your private key from Blockchain.info and importing it in Electrum to see what happens. Online wallets are not recommended anyways for security reasons.