[PROBLEM SOLVED] transaction hash not found

[Mia Chloe]

I am having a bit of an issue here.
I created an Electrum wallet and I later imported the wallet to blue wallet using the seed phrase. After that I tried moving some funds from my wallet across and it seemed to have been broadcasted.
Though the fees I used was low, I tried checking the transaction status on the mempool using the hash but It kept returning an error message saying hash doesn't exist.
I really don't know what move to make or what the problem is exactly.

[1714912909]

1714912909

[1714912909]

1714912909

[1714912909]

1714912909

[1714912909]

1714912909

[1714912909]

1714912909

[AB de Royse777]

Though the fees I used was low, I tried checking the transaction status on the mempool using the hash but It kept returning an error message saying hash doesn't exist.
I really don't know what move to make or what the problem is exactly.

Wait a few minutes. Try with a different explorer. There are no need to panic :-D

[Zaguru12]

If not for privacy sake it will be better you put the transaction ID here. On this my guess is the node of that particular explorer doesn’t have your transaction probably because they purge it out due to low fee or best your transaction wasn’t propagated well. If you’re still seeing it as unconfirmed on the blue wallet maybe that node you’re connected to still has it though. If you have access to the electrum wallet you can switch the server and be able to broadcast the transaction again.

Try blockchair explorer maybe mempool.space doesn’t have your transaction yet

[BlackBoss_]

I tried checking the transaction status on the mempool using the hash but It kept returning an error message saying hash doesn't exist.
I really don't know what move to make or what the problem is exactly.

Some Bitcoin block explorers did not show Pending transactions and you will get error message like this has does not exist.

Try with other block explorers and you will see your pending transaction and its status.
List of useful Bitcoin block explorers.

If you are still panic, copy and paste your public address on a Bitcoin block explorer and check its balance.

[pooya87]

Though the fees I used was low, I tried checking the transaction status on the mempool using the hash but It kept returning an error message saying hash doesn't exist.
I really don't know what move to make or what the problem is exactly.

You should know that there is no single memepool that all nodes share; instead each node has its own mempool and they have different settings that determines what transactions they accept and hold in their mempool.

Without having more details like the fee rate you used, one scenario that can explain what happened to you is this:
Probably you sent your transaction to a node that had a bigger mempool size therefore accepted your tx. However, other nodes rejected it for paying too low fee. So when you visit a block explorer or even possibly connect to another server you don't see the same transaction because it never reached them.

[Stalker22]

~
I really don't know what move to make or what the problem is exactly.

And? Did you manage to find your transaction hash on the mempool and resolve the issue? I see that you were active on the forum very recently, but you did not update this thread about your problem.  I just wanted to check if you were able to figure out the issue by now.

[Mia Chloe]

~
I really don't know what move to make or what the problem is exactly.

And? Did you manage to find your transaction hash on the mempool and resolve the issue? I see that you were active on the forum very recently, but you did not update this thread about your problem.  I just wanted to check if you were able to figure out the issue by now.

I tried every Mempool on 1miau's thread for Blockchain explorers and all still returned a message saying hash not found.
Something tells me my fees were way too small and really don't know what to do or if I should just wait maybe it would probably drop.

[RickDeckard]

If not for privacy sake it will be better you put the transaction ID here. On this my guess is the node of that particular explorer doesn’t have your transaction probably because they purge it out due to low fee or best your transaction wasn’t propagated well. If you’re still seeing it as unconfirmed on the blue wallet maybe that node you’re connected to still has it though. If you have access to the electrum wallet you can switch the server and be able to broadcast the transaction again.

Try blockchair explorer maybe mempool.space doesn’t have your transaction yet

Like Zagaru said, providing the transaction ID would let us be able to analyze your specific situation (or the receiver bitcoin address), if you feel ok with that. Are you sure that your transaction ended up being broadcasted?

[Mia Chloe]

If not for privacy sake it will be better you put the transaction ID here. On this my guess is the node of that particular explorer doesn’t have your transaction probably because they purge it out due to low fee or best your transaction wasn’t propagated well. If you’re still seeing it as unconfirmed on the blue wallet maybe that node you’re connected to still has it though. If you have access to the electrum wallet you can switch the server and be able to broadcast the transaction again.

Try blockchair explorer maybe mempool.space doesn’t have your transaction yet

Like Zagaru said, providing the transaction ID would let us be able to analyze your specific situation (or the receiver bitcoin address), if you feel ok with that. Are you sure that your transaction ended up being broadcasted?

Here is the hash;
c46b6954418e9e09a837dbaa153eddb6619ae413c43c5f83db2d894a92941b8d
Transaction is still not on the mempool

[RickDeckard]

Here is the hash;
c46b6954418e9e09a837dbaa153eddb6619ae413c43c5f83db2d894a92941b8d
Transaction is still not on the mempool

Could you check if you are connectable on the software where you sent your transaction from? If you used Electrum to broadcast it, the bottom right circle on the main graphical interface should be green.

[Mia Chloe]

Here is the hash;
c46b6954418e9e09a837dbaa153eddb6619ae413c43c5f83db2d894a92941b8d
Transaction is still not on the mempool

Could you check if you are connectable on the software where you sent your transaction from? If you used Electrum to broadcast it, the bottom right circle on the main graphical interface should be green.

I didn't use electrum to make the broadcast.
Anyways I just noticed something weird. The transaction seems to have dropped because my balance on my wallet just increased to its initial value before I made the transaction. However my wallet is still displays ( sending transaction). ?

[RickDeckard]

Anyways I just noticed something weird. The transaction seems to have dropped because my balance on my wallet just increased to its initial value before I made the transaction. However my wallet is still displays ( sending transaction). ?

Did you use Blue Wallet then? Check if you are online on it as well:



From my experience, and reading what you just said, something must not be connectable on your end and the transaction ended up being drop by the program before even being broadcasted. Before retrying making another transaction make sure that you are connectable.

[Mia Chloe]

RickDeckard I am kind of confused because the balance reduced again the hash is still not on the Blockchain and mycelium wallet is still displaying sending transaction. I don't know what to do.

[RickDeckard]

RickDeckard I am kind of confused because the balance reduced again the hash is still not on the Blockchain and mycelium wallet is still displaying sending transaction. I don't know what to do.

You could try the following solution provided by nc50lc[1]:

You can cross your fingers and do this:
Update your Mycelium wallet to the latest version, Open it and go to 'Accounts' tab and select the account that has your transaction.
Go to 'Transactions' tab, find the unconfirmed transaction, tap on it to highlight then press menu (...) and select "Delete Unconfirmed Transaction".
If it didn't reappear after the next rescan, then it's now dropped from their mempool and you can now spend its inputs to a new transaction, but I highly doubt it wont.

If your problem still persists, I would try to import your seed words into another wallet and try to broadcast a new transaction from there.
[1]https://bitcointalk.org/index.php?topic=5480683.0

[Zaguru12]

I am kind of confused because the balance reduced again the hash is still not on the Blockchain and mycelium wallet is still displaying sending transaction. I don't know what to do.

Like it was said before your transaction might still be in other node’s mempool or worse still the mycelium wallet is automatically rebroadcasting your transactions and that’s why you seeing it that way and the node they rebroadcast it with has a larger mempool size.

Import your seed phrase into electrum wallet look for server which is shown in the image below, switch between servers and when you see that particular transaction as local then you right click it to delete (although it is not actually deleted from the node that has it) then you make a new transaction with that particular funds make sure you use that particular UTXOs by using the coin control feature.

The logic here is that you’re double spending that transaction, a node that has it already but has full RBF enabled will removed the old one and the one that has it and not full RBF enabled will still keep the old one and reject the new one. But since the fee of the new one is higher there is high chance that it would get confirmed faster than the old one and then invalidate the old one on other nodes.

 Please reply if this as been fixed

[Mia Chloe]

I am kind of confused because the balance reduced again the hash is still not on the Blockchain and mycelium wallet is still displaying sending transaction. I don't know what to do.

Like it was said before your transaction might still be in other node’s mempool or worse still the mycelium wallet is automatically rebroadcasting your transactions and that’s why you seeing it that way and the node they rebroadcast it with has a larger mempool size.

Import your seed phrase into electrum wallet look for server which is shown in the image below, switch between servers and when you see that particular transaction as local then you right click it to delete (although it is not actually deleted from the node that has it) then you make a new transaction with that particular funds make sure you use that particular UTXOs by using the coin control feature.

The logic here is that you’re double spending that transaction, a node that has it already but has full RBF enabled will removed the old one and the one that has it and not full RBF enabled will still keep the old one and reject the new one. But since the fee of the new one is higher there is high chance that it would get confirmed faster than the old one and then invalidate the old one on other nodes.

 Please reply if this as been fixed

Thanks alot for the effort.
I was able to fix the issue yesterday. I finally got to know that the fee I used was way too low about 11sat/byte like what was wrong with me?. Anyways the problem was mycelium node was constantly rebroadcasting it even when the network purged it out. So I had to use my seed to access the wallet through blue wallet then I was able to stop the transaction and move the funds without stress but with a better fee.

[Lucius]

I finally got to know that the fee I used was way too low about 11sat/byte like what was wrong with me?
~snip~

I'm wondering the same thing - because you're not a beginner who should have a problem with checking the status of mempool and fees before making a transaction.

In addition, my advice to you is not to play too much with your seed by entering it into different wallets if there is no need for it. By doing such things, you only expose yourself to the risk of entering a seed into a fake wallet or of the device being infected with malware at some point. Find a wallet that suits you and stick to it - and if you want to try a new wallet, simply install it and create a new seed for that wallet.

[satscraper]

finally got to know that the fee I used was way too low about 11sat/byte

I would say 11sat/byte is extremely low even  for the current mempool state. For instance, currently, mempool.space is purging  all transactions with fee less than 21.5 sat/vB.



I think it is always a wise approach  to check this value and set up the fee above it before sending any transaction.

[Mia Chloe]

In addition, my advice to you is not to play too much with your seed by entering it into different wallets if there is no need for it. By doing such things, you only expose yourself to the risk of entering a seed into a fake wallet or of the device being infected with malware at some point. Find a wallet that suits you and stick to it - and if you want to try a new wallet, simply install it and create a new seed for that wallet.

This was exactly what I did after I resolved the issues I formated my device and reinstalled my initial wallet software I am familiar with. I definitely can't risk exposing my seed phrase as it is not a wise decision to access your wallet too frequently with your seed phrase just like you mentioned.

I would say 11sat/byte is extremely low even  for the current mempool state. For instance, currently, mempool.space is purging  all transactions with fee less than 21.5 sat/vB.

I think it is always a wise approach  to check this value and set up the fee above it before sending any transaction.

Yes that's very true I normally check the Mempool before I make transactions and of recent I make use of the Mempool Observer Topic by stompix before I make my transactions. I was kind of carried away when I made that transaction. Anyways every mistake is a chance to learn something new. Now I can help someone if he eventually gets into a problem similar to mine.
Thanks to everyone here for your collective assistance.

[RickDeckard]

Happy to know you sorted it out. My recommendation for you would be to first edit the thread title marking your problem as "Solved", editing your first thread with the method that solved the problem and then close the thread. This way it can help future users with the same problem while blocking further unnecessary bumps.