BTC Tx from BC Wallet pending for 9 months, explorers do not recognize Tx Hash

Hi everyone here,

I'm new here and still finding my way around and in desperate need for help.

I have a bitcoin transaction made from my Blockchain.com Wallet on the 30th of Dec, 2023 which is still in pending state as I write. I watched tons of videos over the months, and it led me to trying Electrum wallet, unfortunately, it did not recognize the transaction upon importing my seed phrase. It's as though this Tx does not exist, I can only see it on Blockchain.com explorer and under my BC Wallet tx history, nowhere else!

Please help me if you know how to get this money back. It's a little over $500.

Tx ID: 44c40afcccc7f23065559178ab1d33e506a46d65c7a52d564cb791247652eb3a

https://www.blockchain.com/explorer/transactions/btc/44c40afcccc7f23065559178ab1d33e506a46d65c7a52d564cb791247652eb3a

You have a couple of options.
Two of which are either re-broadcast the transaction or import your backup phrase to another wallet where you can (re)spend the inputs of that transaction.

The former is easy since all you have to do is to broadcast your transaction with a Bitcoin client or blockexplorer like https://blockstream.info/tx/push,
However, if the recipient isn't you, it will be sent to the original recipient once you re-broadcast since it's the same transaction.

Here's your raw transaction in hex:

Code:

0100000002e400d01a5722845c53c04341922f361cb3694f667873d6e8401c82de56865b6c000000006b483045022100e9e8c984d1a9168c1a88debcc8c3fbd4763c9581dee23979913b440c0c2bb68002206e68cf2a79c5a360c9696b1bb385ab84309e01fe1194ad24330ce2bfaadfb3ce012103366ab1b806d62406d0dd8bce2699a7715f16e5ceb7756dd77a9a3e9efa6f09c8ffffffff153098d545f4b6f8b6a1a1e5d78361fdacb828c02d4fecc7eafe4537360d3f96000000006b4830450221008e3b5c916cfdc71b9a9fb81dfa7f4f73282e47a9b799e52ce3386f1b13270618022037848abfaa40defdaccaa266330867414936ecc61caa5af88044c49dd9a44f64012103366ab1b806d62406d0dd8bce2699a7715f16e5ceb7756dd77a9a3e9efa6f09c8ffffffff0200050e00000000001976a914e33058858cf4a0b9b59653bc37b9d4972c9f436188ac14ac0c0000000000160014713211eb16ad60224672a75b1827c307cd5c1bcc00000000

I checked it with testmempoolaccept on my node and it's still valid and the fee is "alright" but not at the top.
To others: Let OP decide, please do not broadcast it!

The latter requires a whole set of instructions, I'll provide you a step-by-step instructions if you prefer it.

Odd, I thought blockchain.com wallets kept rebroadcasting.

Is the 3 sat/vb fee that their explorer is showing accurate?

If so it never would have cleared back then. If he rebroadcasts now it should clear in the next block or 2, once again if it really is 3 sat/vb

-Dave

Quote from: DaveF on October 05, 2024, 01:01:44 PM

Odd, I thought blockchain.com wallets kept rebroadcasting.

This is the second case that I've seen so far and I think they do not re-broadcast.

Based from those two cases, Blockchain's wallet keeps the expired transaction and their API might be keeping it on the server-side.
The side effect is, their wallet transactions will never drop unless it's conflicted with another transaction.
It would never get a good chance of confirmation since its already dropped by the majority of the nodes.

Someone must have rebroadcasted it, as it has 11 confirmations now. It's weird their block explorer kept it since 30 Dec 2023, but doesn't broadcast it.

Quote from: nc50lc on October 05, 2024, 02:31:54 PM

Quote from: DaveF on October 05, 2024, 01:01:44 PM

Odd, I thought blockchain.com wallets kept rebroadcasting.

Ah, the good old blockchain.com quality strikes again.

Shrug, it is what it is and for some reason people keep using them.

Quote from: LoyceV on October 05, 2024, 03:01:29 PM

Someone must have rebroadcasted it, as it has 11 confirmations now. It's weird their block explorer kept it since 30 Dec 2023, but doesn't broadcast it.

That or something else triggered it, once again long ago fuzzy memory I always thought there was a way to do it from their wallet. I was wrong on the re-broadcasting so I might be misremembering here too. It's been a while since I even looked at a wallet on their website for someone.

-Dave

Weird transaction even it was stuck for almost 9 months I assumed that nc50lc had not noticed that the transaction had been confirmed, but blockchain explorer contains some missing information, such as when it was confirmed by checking the TX on mempool.space, it confirmed 45 minutes ago, and the transaction was broadcasted 8 hours ago. It means someone tried to rebroadcast the TX 8hrs ago.

Isn't that this transaction was made with time lock?

Quote from: BitMaxz on October 05, 2024, 10:00:04 PM

A better question is whether the OP needed the transaction to be confirmed now at all. He did not describe the purpose of sending Bitcoin to that address, I guess it was not a one-time need, because in that case, he threw money away.

Quote from: BitMaxz on October 05, 2024, 10:00:04 PM

Weird transaction even it was stuck for almost 9 months I assumed that nc50lc had not noticed that the transaction had been confirmed,

The transaction was missing in all blockeplorers except Blockchain's, you can safely assume that it was dropped by the majority of the nodes.
If it's just a simple misconception, it would've got a confirmation already sometime along those 9 months when the fee rate is even lower than 3sat/vB.

I didn't broadcasted it yesterday and let OP decide if he want it to proceed or make a replacement using other client.

So it's either OP broadcasted it but didn't replied or someone took the liberty to do it.
Anyways, it's apparent that he wanted the transaction to proceed based from his post.

Quote from: BitMaxz on October 05, 2024, 10:00:04 PM

~~~

Quote from: https://mempool.space/tx/44c40afcccc7f23065559178ab1d33e506a46d65c7a52d564cb791247652eb3a

Timestamp ‎2024-10-05 13:38:07 (1 day ago)
Confirmed After 44 minutes

mempool.space says it confirmed 44 minutes after their mempool saw the transaction. Block confirmation time was 13:38 UTC, so the transaction has been newly broadcasted around 12:54 UTC yesterday (you posted at 22:00 UTC, a little more than 9h after broadcast, hm, I thought your 8h were off a bit more, now I see it's pretty close).

Quote from: BitMaxz on October 05, 2024, 10:00:04 PM

Isn't that this transaction was made with time lock?

Don't see a clue for this, locktime is zero.

Quote from: nc50lc on October 06, 2024, 03:54:09 AM

Blockchain explorer has some missing information, which leads me to believe that it was confirmed in the past, possibly in December, until I check the transaction in another explorer that provides more information than blockchain.com explorer. I thought that you didn't notice it, but I'm the one who was mistaken due to a lack of information from blockchain.com. Anyway, thanks for the clarification.

Hi everyone;D

Please pardon me if my method of response is messy. I'm really struggling to understand how this platform works, and how to properly reply. I just stumbled on the platform yesterday by mere luck but guess what guys? You guys have successfully resolved this issue for me! Someone probably broadcasted it here following the raw tx hex @nc50lc shared, and it is now confirmed. The recipient wallet is also mine, it belongs to my local wallet so no loss was made. I cannot thank you all enough for this invaluable help! Not only was $500+ dollars pending for over 9months, my change address holding the balance of the tx was also useless, I couldn't send the change. So essentially you have helped me recover over $1k!

I'm so elated! I've tried Electrum and BTC accelerators, none worked but you guys did it! May God bless you all Kiss

Special thanks to nc50lc and the person who advise me to create a new post! I also thank everyone that contributed, and I will try to stay in touch on this platform so I can learn more and also pay it forward! Muchas gracias a todos!

Bitcoin Memory Pool
Waiting for confirmation: a series about mempool and relay policy

OP got his transaction confirmed after many months. Waiting for many months without ideas on what's happening with the unconfirmed transaction is not comfortable experience.

These guides can help OP in future. I quote two notes for OP.
If an unconfirmed transaction is more than 14 days since a broadcasting time, it can be time to consider of bumping fee rate or re-broadcast it.

Quote

The default mempool expiry time is 2 weeks. It used to be 3 days, but it was increased to 14 days in 2017 with the release of Bitcoin Core v0.14.0.
When a transaction leaves the memory pool, it's as though it never happened. So don't rely on memory pool transactions when accepting payments. If the transaction leaves the memory pool without getting mined, then it might as well have never taken place. The only way for getting it back in to the memory pool would be to re-broadcast to the network.

Quote from: Cryptonewbiee on October 07, 2024, 12:00:41 AM

You're welcome.

Quote from: Cryptonewbiee

The recipient wallet is also mine, it belongs to my local wallet so no loss was made.

I can tell that much based from the context of the OP.

I was thinking to send the RAW transaction via PM but with the availability of the TXID,
anyone who can use Blockchain's API will be able to rebroadcast it whether I post it or not anyways.

Quote from: SquirrelJulietGarden on October 07, 2024, 03:14:04 AM

These guides can help OP in future. I quote two notes for OP.
If an unconfirmed transaction is more than 14 days since a broadcasting time, it can be time to consider of bumping fee rate or re-broadcast it.

Problem is; Blockchain(dot)com doesn't abide with those standards: their online wallet keeps transactions even after being dropped from their mempool.
And they don't have an option to abandon/remove or rebroadcast an expired transaction or even full/opt-in RBF option to bump a transaction's fee.
That essentially locks the user's coins until it get rebroadcast->confirmed or conflicted with a confirmed replacement txn.