Hey folks, I sent a transaction using Bitcoin Core on December 4, 2023, and now it’s December 17, 2023. I totally forgot to add a decent fee. When I check the transaction in Bitcoin Core, it shows it's in the mempool, but when I enter the TXID on mempool.space, it says it’s waiting for the transaction to hit the mempool. Can anyone help me get this transaction confirmed? My TXID is below, thanks a lot!
9004ca93cf578578463f141a5f3132735a418ae015c176debfebf612b31d4a0d
I also tried checking the TX on Mempool and it said the same thing, maybe this could be as a result of the transaction not being broadcasted yet, Im not too sure but I think it should be it because any transaction which has been broadcasted even if its not confirm yet could be able to be seen on mempool and other block explorer
One of my personal nodes has a mempool size of 1GB and I checked with the presence of your transaction in my node's mempool. This Tx is not in my mempool either, response to above command was
Very likely it has been dropped from most if not all node's mempool when also https://mempool.space/ doesn't know about the transaction.
The transaction is over 2 weeks and most nodes have dropped the transaction from their mempool. You should be able to see your coins on your wallet balance and be able to rebroadcast it in another transaction.
I tried to find your transaction in some block explorers and none of them had your transaction.
So, it seems that your transaction has not been broadcasted at all and it's displayed only in your wallet.
Right-click on your transaction and see if there's "abandon transaction" option. If so, click on it and after that, you will be able to make a new transaction.
I checked multiple blockchain explorers and nodes, your TXID doesn't exist. This means you should be able to create a new transaction and spend the same inputs (UTXOs). Make sure your wallet is fully synced. Right-click on an unconfirmed transaction to pop up a contextual menu and check if it has the option "Abandon transaction".
edit: it seems that hosseinimr93 was faster while I was still writing my post...
Your transaction has been dropped by the nodes, which means the balance should be available for you to spend now again so your qt might be having issues with sync.
Try 'listunspent' command and see whether the UTXOs appear as spendable.
If using Bitcoincore is not convenient then import the address into Electrum using privatekeys and spend it from there.
To get your private keys use 'dumpprivkey' followed by the respective address.
Have you set any configurations related to transaction relay or mempool in your bitcoin.conf file, GUI settings or command line options?
Because it may be broadcasted exclusively to your node due to a setting that allows it (thus the "in mempool" note) but rejected by all your peers for some reason.
Since you already willing to share the transaction via txid which we can't find, it's better if you can share the raw transaction for us to see the actual issue.
Get it from the 'Transaction' tab of the GUI, right-click on it and select "Copy raw transaction" or via getrawtransaction command.
Then put it inside [code][/code] tags so the forum wont mess its format.
In case that you want to abandon it as suggested by others, you'll have to get it out of your mempool first before the "abandon transaction" option can be clicked.
One way is to remove the option that allows it to your mempool which is at the same time allowing you to create transactions that'll have trouble with propagation.
Or the manual removal of mempool.dat (Bitcoin Core must not be running) and temporarily setting walletbroadcast=0 to be able to abandon it.
There is no way to make this transaction. The transaction is trying to spend coins that have been already spent and it's invalid.
If you broadcast this transaction, you would get "bad-txns-inputs-missingorspent" error.
Edit:
Here is the transaction in which the coins were spent.
b89e85a68f317063e7d38527d5bd559b5eca1911d1e71a6cb82abfba529cc3db
Okay as said above, its inputs are already spent.
Your wallet probably able to make and broadcast such transaction because it failed to scan the transaction that spent it.
Using rescanblockchain command (instructions) should update your balance to reflect the correct transactions and available UTXO to spend. (since those're spent, those shouldn't be available)
But if your node is pruned, you wouldn't be able to rescan the whole blockchain but only from the lowest block height that your node has.
After the rescan, it should be dropped from your mempool.