<p><strong>According to your description (having problems while syncing full node), I wonder if your &quot;unconfirmed transaction&quot; is really unconfirmed? Is it already confirmed, or discarded (due to double-spending etc)?</strong></p>
<p><strong>The first problem: &quot;stuck&quot; 0-confirmation transaction</strong></p>
<p>First of all, replace-by-fee is there to deal with &quot;low-fee stuck transactions&quot; problem, you would be able to bump fee with ease if the transaction had RBF enabled.</p>
<p>If your stuck transaction is not so urgent, you may just wait for the mempool to be cleared naturally, then your transaction will finally be confirmed, since the mempool is not so crowded (like old times in 2017) nowadays.</p>
<p>Just watch the last &quot;Mempool size in MB&quot; chart here: <a href="https://core.jochen-hoenicke.de/queue/#24h" rel="nofollow noreferrer">https://core.jochen-hoenicke.de/queue/#24h</a></p>
<p>If you want to &quot;accelerate&quot; or &quot;revert&quot; this transaction, you have two options.</p>
<p>The first option: you may contact a mining pool which provides &quot;transaction accelerating (prioritising)&quot; service, like <a href="https://pushtx.com/" rel="nofollow noreferrer">Poolin</a> or <a href="https://pushtx.btc.com/" rel="nofollow noreferrer">BTC.COM</a>. However, this option can be expensive, and, there won't be any refund.</p>
<p>The second option: &quot;double-spend&quot; by yourself with Electrum, which is usually much cheaper than transaction prioritising services mentioned above, but a bit complicated.</p>
<ol>
<li><p>Find out the previous transaction(s) which the stuck transaction is spending from. You may use the <code>getrawtransaction STUCK_TXID true</code> (replace <code>STUCK_TXID</code> with your own stuck transaction ID) command in debug console of Bitcoin Core, or just query it on an online block explorer like <a href="https://blockstream.info" rel="nofollow noreferrer">https://blockstream.info</a>.</p>
<p>Blockstream explorer shows previous outpoints clearly, where the outpoint is represented in <code>TXID(long alphanumeric text string):INDEX(number)</code> format. For <a href="https://blockstream.info/tx/4f3740af2ddd4cea2fcf48332488c1f3d6a01764bf27f3ca9d54574b5a1d8c2e" rel="nofollow noreferrer">example</a>: this transaction spent 2 previous transactions, which have TXIDs of <code>00f5854cebdcd318edd325ab07e4157964f225a659302f3f5949ffe07020db4e</code> and <code>6d4a34592200324f716a92d8d84db8c85bc97189610b1d4bee4fcb7d56713857</code></p>
</li>
<li><p>Copy raw transaction data of previous transaction(s). You may simply double-click each transaction showed on Bitcoin Core GUI in turn, to find them by transaction ID, and then right-click -&gt; <code>Copy raw transaction</code>.</p>
<p>You may also use the <code>getrawtransaction PREVIOUS_TXID</code> command instead, you need to run this command separately on each <code>PREVIOUS_TXID</code>, if multiple previous transactions were spent.</p>
</li>
<li><p>Create a new Electrum wallet on an offline device, then choose the <code>Import Bitcoin addresses or private keys</code> option.</p>
</li>
<li><p>Import your private keys to Electrum. The wallet won't sync, because there's no internet - that's fine, because we don't want Electrum to fetch back the stuck transaction.</p>
</li>
<li><p>Import the previous transaction(s) by clicking <code>Tools</code> menu -&gt; <code>Load transaction</code> -&gt; <code>From text</code>.</p>
</li>
<li><p>Click the <code>View</code> menu -&gt; <code>Show Coins</code> to show the <code>Coins</code> tab. Then switch to the <code>Coins</code> tab, select all of them, and right-click -&gt; <code>Spend</code>.</p>
<p>Of course, if you are sure about exactly which coins were spent, you won't need to spend all available coins this time, which could reduce the fee cost a bit - but this situation is relatively rare. To keep yourself from off-by-one human errors, you'd better just spend all of them.</p>
</li>
<li><p>Now, you are about to construct a double-spending transaction which will send these coins back to your own wallet, or any other address(es) you want, by clicking <code>Preview</code> button. This time you should choose a higher fee rate (sat/Byte), at least higher than the stuck transaction.</p>
<p>By the way, it is highly recommended to enable replace-by-fee on this transaction, in case of further fee-bumping.</p>
</li>
<li><p>Electrum is able to show QR code of this double-spending transaction. Use another online device to scan it with Electrum, then it could be sent out. You may also try to send it directly after reconnecting the device to Internet.
If the stuck transaction has not yet expired on the Electrum server you are using, broadcasting the double-spending transaction might face some errors. You may try to broadcast it through other methods, eg. block explorers, and <code>sendrawtransaction</code> of Bitcoin Core.</p>
</li>
</ol>
<p><strong>The second problem: Bitcoin Core full node is painful to sync</strong></p>
<p>First, the performance bottleneck usually lies at frequent I/O operations on the <code>chainstate</code> subdirectory, which stores the UTXO database, especially the data directory was placed on an HDD (which is supposed to make the situation worse if the HDD is SMR).</p>
<p>Second, currently, I'm personally not in favor of pruning, because almost all historical transaction history (which is exactly what the gigantic block chain contains) is discarded, thus rescanning becomes limited within recent blocks only. Rescanning happens if you are importing keys/addresses/wallet.dat, or <code>zapwallettxes</code>. In the future, this problem might be finally relieved by some <a href="https://github.com/bitcoin/bitcoin/pull/15946" rel="nofollow noreferrer">improvements</a>.</p>
<p>If your computer has plenty of available RAM, you may allocate more than 6GB (depends on historical peak UTXO size) of RAM for the database cache (see the <code>Options</code> window) of Bitcoin Core. This tweak effectively removes the I/O bottleneck. (well, you may still face this problem if you are catching up from some date before, you may <code>cat</code> (Linux/Mac) or <code>type</code> all files (use the <code>*</code> wildcard) into <code>/dev/null</code> (Linux/Mac) or <code>nul</code> (Windows) to force the OS to read them once, then they could be cached into the RAM)</p>
<p>If you have both HDD and SSD, you can configure the <code>blocksdir</code> parameter to migrate the gigantic block chain to a cheap-but-slow HDD, while keeping the frequently-accessed <code>chainstate</code> etc on a fast-but-expensive SSD.</p>

CC BY-SA 4.0
2019-10-21T00:04:43.170Z
Thank you for your answer. You offer way more than coinbase customer support (who my stuck transaction is to). Is there anything they can do? They barely return my emails. I told them the could debit my account the fee to get the block confirmed. I don't think they even understand what's going on. I'm worried they are going to change my btc coinbase receiving address. It's going on 2 weeks now. At this point I wouldn't recommend coinbase to anyone.
dave
CC BY-SA 4.0
2019-10-21T00:12:48.430Z
I've done transactions with coinbase before but never had a problem. I'm just so disappointed with there understanding of everything. They are basically turning me into a programmer for one transaction. They should have to give me a job as head of engineering after this. People respond to me on this platform more than coinbase does about my stuck transaction. And they are supposed to be a billion dollar company. Than stack exchange is a trillion dollars company. I've lost faith in even getting this transaction back and am starting to think fiat has its benefits. Coinbase is awful.
dave
CC BY-SA 4.0
2019-10-21T02:57:14.840Z
I have checked the mempool and block size status just now, it seems that even the transactions which paid the lowest 1sat/Byte fee could already have been confirmed. Is your "unconfirmed transaction" really unconfirmed? If you still have problems with your full node, you may check that "unconfirmed transaction" on an online block explorer.
Chris Chen
CC BY-SA 4.0
2019-10-21T03:00:40.867Z
Pointing fingers at Coinbase or someone else cannot solve the problem. Theoritically, Coinbase could do the "child-pay-for-parent" (Electrum provides this feature directly to both sender and receiver, but it's more expensive than RBF however) trick to bump the fee, thus prioritising the stuck transaction. However, they might have their own wallet management policies which may sacrifice convenience and flexibility in exchange for security.
Chris Chen
CC BY-SA 4.0
2019-10-21T03:13:22.713Z
If coinbase provides a new depositing address to you, this should be totally fine, Coinbase guaranteed that "all addresses that have been generated for your account will remain associated with your account forever" here: https://support.coinbase.com/customer/en/portal/articles/2276500-why-did-my-wallet-address-change-
Chris Chen
CC BY-SA 4.0
2019-10-21T11:56:33.753Z
Blockchain.info doesn't recognize my hash. But my btc qt wallet is still debited. I'm upgrading now. And it's taking forever to sync. I know people don't like me criticizing coinbase but the day before there was no problem. I'm on my 15th day now. No result. No email or correspondence from them to eliviate my concerns or remedy they can offer. So I just want to make it aware to the crypto community about coinbase.
dave
CC BY-SA 4.0
2019-10-21T12:18:20.717Z
I will provide a bounty for anyone who can remedy this situation for me. I made the same offer to coinbase. No response though. Thank you.
dave
CC BY-SA 4.0
2019-10-21T18:35:16.667Z
You may lookup your address balance (and related transaction history) on an online block explorer. It sounds harsh, but, I don't think it's impossible - maybe your bitcoin wallet had already been compromised, thus your depositing transaction became an invalid double-spend which was discarded by the network, and, you didn't notice that because your full node had problem to sync.
Chris Chen
CC BY-SA 4.0
2019-10-21T18:42:47.967Z
Once you have confirmed your bitcoins are still on your own addresses, you can simply import the private key to other wallet (like Electrum) to send these coins to anywhere you want.
Chris Chen
CC BY-SA 4.0
2019-10-21T22:15:03.827Z
The day before this fiasco I made a transaction with coinbase. No problem. The next one, nothing. I can't even find the hash on blockchain.info. I am upgrading my node now and is taking forever to sync. It's been more than two weeks. What's the longest time a block sat in the mempool? I still want the transaction to go through. On the dread forum there is already complaints about coinbase. Now the cleaner can know.
dave
CC BY-SA 4.0
2019-10-21T22:16:42.690Z
Sorry clearnet*
dave
CC BY-SA 4.0
2019-10-21T23:17:50.210Z
Although most nodes (especially the ones used by mining pools) have a expiration time, there's no guarantee that an unconfirmed (0-conf) transaction will be forgot by every node. As long as the transaction is still valid, it's still possible for someone who didn't discard this transaction to rebroadcast it (or to directly include it in the block, for miners/mining pools).
Chris Chen
CC BY-SA 4.0
2019-10-21T23:35:27.563Z
Recently the mempool usually clears within one day. So, it's quite unusual for me that a transaction could wait for such a long period to confirm. You may copy the raw transaction from Bitcoin Core, then you can rebroadcast it with a block explorer like blockchain.info (or with the sendrawtransaction command). However, to ensure your wallet has not been compromised, you'd better check the balance and transaction history of your previous address on a block explorer. (you may do this with Tor browser to protect your privacy)
Chris Chen
CC BY-SA 4.0
2019-10-20T17:07:06.580Z
2019-10-20T17:40:29.263Z
2020-06-16T11:10:03.350Z
Chris Chen
<p>It's not possible to remove your transmitted transaction from the network. </p>

<p>Even if you shut down and clean your own local client, other clients around the world have it in their mempool. That's why your local client reflects the balance minus the amount you sent, even though it's not confirmed. That's how it's supposed to work, Bitcoin TX's are supposed to be irreversible even before being mined.</p>

<p>So, Bitcoin does not have a TX revocation network message available. </p>

<p>Only thing you can do is, before this unwanted TX is confirmed, to use another client, which either didn't see your TX or allows you to craft TX's and broadcast them, to submit a new transaction containing a much higher fee and same UTXO's. (Double spending on purpose.)</p>

<p>This new TX will cost you the fee, but if you set your own address as beneficiary, the funds will return to your wallet and the old transaction will get discarded by the network as a double spend. This higher fee is your cost to revoke the old unwanted TX. All this has to be done before the old TX is confirmed in a block.</p>

CC BY-SA 4.0
2019-10-20T17:05:03.820Z
Do you recommend a client/wallet that won't rebroadcast the tx? I don't want to be too much of a bother but could you refer a link so I can get back my satoshis. Any help would be appreciated. Thanks.
dave
CC BY-SA 4.0
2019-10-20T19:23:21.697Z
You can use Bitcoin Core itself to create a raw transaction. Then you send the funds to yourself using a bigger fee: https://stackoverflow.com/questions/38493893/heres-how-to-send-raw-transaction-btc-using-bitcoin-cli-command
Jose Fonseca
CC BY-SA 4.0
2019-10-22T01:53:07.410Z
Blockchain.info doesn't even recognize the hash. Can you explain why?
dave
CC BY-SA 4.0
2019-10-20T14:34:35.447Z
2019-10-20T14:34:35.447Z
Jose Fonseca
<p>I am running a node with an unconfirmed transaction. I tried shutting down my btc qt so the transaction would be forgotten. To no avail it keeps rebroadcasting the transaction. I am in the process of upgrading and syncing my btc qt now too. But it's taking forever to sync. What will happen if I import my keys to a software wallet, electrum? Will my electrum wallet be made whole from the unconfirmed transaction? Any suggestions? I'm not in love with running a node anymore or coinbases ability to retrieve my transaction. Coinbase was the supposed recipient. It's been two weeks.</p>

CC BY-SA 4.0
2019-10-19T21:16:04.577Z
Possible duplicate of [How do I get rid of an unconfirmed transaction on Bitcoin Core 0.14.1?](https://bitcoin.stackexchange.com/questions/54284/how-do-i-get-rid-of-an-unconfirmed-transaction-on-bitcoin-core-0-14-1)
chytrik
CC BY-SA 4.0
2019-10-20T14:53:13.500Z
If you once provided "zapwallettxes" parameter to bitcoin-qt, it would start rescan process, this would be more tricky if you had pruning enabled...
Chris Chen
CC BY-SA 4.0
2019-10-20T14:54:34.540Z
It's possible to make your own node forget the unconfirmed transaction, but the process would be a little complicated: https://en.bitcoin.it/wiki/Fee_bumping#Bitcoin_Core_GUI You would need to temporarily break connectivity. You also have to be sure that the newer transaction is spending same coins with the older transaction, thus the two transactions would conflict with each other. You are still not able to make every node on the network to forget the unconfirmed transaction transaction, that's why you should do such "double-spend".
Chris Chen
CC BY-SA 4.0
2019-10-20T16:14:14.527Z
Should I export my keys to a software wallet, like electrum? How do I actually do the double spend? Can you refer a link or bitchute channel? Or something, lol. It's been two weeks and I'm kind of getting worried about coinbase. That's who the transaction was to. Do you know if they offer any customer service to remedy this?
dave
<bitcoin-core><unconfirmed-transactions><electrum>
Unconfirmed transaction. How to make my wallet made whole
dave
# Unconfirmed transaction. How to make my wallet made whole

(Asked by: username_0 on 2019-10-19)

I am running a node with an unconfirmed transaction. I tried shutting down my btc qt so the transaction would be forgotten. To no avail it keeps rebroadcasting the transaction. I am in the process of upgrading and syncing my btc qt now too. But it's taking forever to sync. What will happen if I import my keys to a software wallet, electrum? Will my electrum wallet be made whole from the unconfirmed transaction? Any suggestions? I'm not in love with running a node anymore or coinbases ability to retrieve my transaction. Coinbase was the supposed recipient. It's been two weeks.

**Tags:** bitcoin-core, unconfirmed-transactions, electrum

> **Comments:**
> **username_1**: Possible duplicate of [How do I get rid of an unconfirmed transaction on Bitcoin Core 0.14.1?](https://bitcoin.stackexchange.com/questions/54284/how-do-i-get-rid-of-an-unconfirmed-transaction-on-bitcoin-core-0-14-1)  
> **username_2**: If you once provided "zapwallettxes" parameter to bitcoin-qt, it would start rescan process, this would be more tricky if you had pruning enabled...  
> **username_2**: It's possible to make your own node forget the unconfirmed transaction, but the process would be a little complicated: https://en.bitcoin.it/wiki/Fee_bumping#Bitcoin_Core_GUI You would need to temporarily break connectivity. You also have to be sure that the newer transaction is spending same coins with the older transaction, thus the two transactions would conflict with each other. You are still not able to make every node on the network to forget the unconfirmed transaction transaction, that's why you should do such "double-spend".  
> **username_0**: Should I export my keys to a software wallet, like electrum? How do I actually do the double spend? Can you refer a link or bitchute channel? Or something, lol. It's been two weeks and I'm kind of getting worried about coinbase. That's who the transaction was to. Do you know if they offer any customer service to remedy this?  

---

## 2 answers

### Answer by username_2 on 2019-10-20. Score: 0

**According to your description (having problems while syncing full node), I wonder if your "unconfirmed transaction" is really unconfirmed? Is it already confirmed, or discarded (due to double-spending etc)?**

**The first problem: "stuck" 0-confirmation transaction**

First of all, replace-by-fee is there to deal with "low-fee stuck transactions" problem, you would be able to bump fee with ease if the transaction had RBF enabled.

If your stuck transaction is not so urgent, you may just wait for the mempool to be cleared naturally, then your transaction will finally be confirmed, since the mempool is not so crowded (like old times in 2017) nowadays.

Just watch the last "Mempool size in MB" chart here: <https://core.jochen-hoenicke.de/queue/#24h>

If you want to "accelerate" or "revert" this transaction, you have two options.

The first option: you may contact a mining pool which provides "transaction accelerating (prioritising)" service, like [Poolin](https://pushtx.com/) or [BTC.COM](https://pushtx.btc.com/). However, this option can be expensive, and, there won't be any refund.

The second option: "double-spend" by yourself with Electrum, which is usually much cheaper than transaction prioritising services mentioned above, but a bit complicated.

1. Find out the previous transaction(s) which the stuck transaction is spending from. You may use the `getrawtransaction STUCK_TXID true` (replace `STUCK_TXID` with your own stuck transaction ID) command in debug console of Bitcoin Core, or just query it on an online block explorer like <https://blockstream.info>.

   Blockstream explorer shows previous outpoints clearly, where the outpoint is represented in `TXID(long alphanumeric text string):INDEX(number)` format. For [example](https://blockstream.info/tx/4f3740af2ddd4cea2fcf48332488c1f3d6a01764bf27f3ca9d54574b5a1d8c2e): this transaction spent 2 previous transactions, which have TXIDs of `00f5854cebdcd318edd325ab07e4157964f225a659302f3f5949ffe07020db4e` and `6d4a34592200324f716a92d8d84db8c85bc97189610b1d4bee4fcb7d56713857`
2. Copy raw transaction data of previous transaction(s). You may simply double-click each transaction showed on Bitcoin Core GUI in turn, to find them by transaction ID, and then right-click -> `Copy raw transaction`.

   You may also use the `getrawtransaction PREVIOUS_TXID` command instead, you need to run this command separately on each `PREVIOUS_TXID`, if multiple previous transactions were spent.
3. Create a new Electrum wallet on an offline device, then choose the `Import Bitcoin addresses or private keys` option.
4. Import your private keys to Electrum. The wallet won't sync, because there's no internet - that's fine, because we don't want Electrum to fetch back the stuck transaction.
5. Import the previous transaction(s) by clicking `Tools` menu -> `Load transaction` -> `From text`.
6. Click the `View` menu -> `Show Coins` to show the `Coins` tab. Then switch to the `Coins` tab, select all of them, and right-click -> `Spend`.

   Of course, if you are sure about exactly which coins were spent, you won't need to spend all available coins this time, which could reduce the fee cost a bit - but this situation is relatively rare. To keep yourself from off-by-one human errors, you'd better just spend all of them.
7. Now, you are about to construct a double-spending transaction which will send these coins back to your own wallet, or any other address(es) you want, by clicking `Preview` button. This time you should choose a higher fee rate (sat/Byte), at least higher than the stuck transaction.

   By the way, it is highly recommended to enable replace-by-fee on this transaction, in case of further fee-bumping.
8. Electrum is able to show QR code of this double-spending transaction. Use another online device to scan it with Electrum, then it could be sent out. You may also try to send it directly after reconnecting the device to Internet.
   If the stuck transaction has not yet expired on the Electrum server you are using, broadcasting the double-spending transaction might face some errors. You may try to broadcast it through other methods, eg. block explorers, and `sendrawtransaction` of Bitcoin Core.

**The second problem: Bitcoin Core full node is painful to sync**

First, the performance bottleneck usually lies at frequent I/O operations on the `chainstate` subdirectory, which stores the UTXO database, especially the data directory was placed on an HDD (which is supposed to make the situation worse if the HDD is SMR).

Second, currently, I'm personally not in favor of pruning, because almost all historical transaction history (which is exactly what the gigantic block chain contains) is discarded, thus rescanning becomes limited within recent blocks only. Rescanning happens if you are importing keys/addresses/wallet.dat, or `zapwallettxes`. In the future, this problem might be finally relieved by some [improvements](https://github.com/bitcoin/bitcoin/pull/15946).

If your computer has plenty of available RAM, you may allocate more than 6GB (depends on historical peak UTXO size) of RAM for the database cache (see the `Options` window) of Bitcoin Core. This tweak effectively removes the I/O bottleneck. (well, you may still face this problem if you are catching up from some date before, you may `cat` (Linux/Mac) or `type` all files (use the `*` wildcard) into `/dev/null` (Linux/Mac) or `nul` (Windows) to force the OS to read them once, then they could be cached into the RAM)

If you have both HDD and SSD, you can configure the `blocksdir` parameter to migrate the gigantic block chain to a cheap-but-slow HDD, while keeping the frequently-accessed `chainstate` etc on a fast-but-expensive SSD.

> **Comments:**
> **username_0**: Thank you for your answer. You offer way more than coinbase customer support (who my stuck transaction is to). Is there anything they can do? They barely return my emails. I told them the could debit my account the fee to get the block confirmed. I don't think they even understand what's going on. I'm worried they are going to change my btc coinbase receiving address. It's going on 2 weeks now. At this point I wouldn't recommend coinbase to anyone.  
> **username_0**: I've done transactions with coinbase before but never had a problem. I'm just so disappointed with there understanding of everything. They are basically turning me into a programmer for one transaction. They should have to give me a job as head of engineering after this. People respond to me on this platform more than coinbase does about my stuck transaction. And they are supposed to be a billion dollar company. Than stack exchange is a trillion dollars company. I've lost faith in even getting this transaction back and am starting to think fiat has its benefits. Coinbase is awful.  
> **username_2**: I have checked the mempool and block size status just now, it seems that even the transactions which paid the lowest 1sat/Byte fee could already have been confirmed. Is your "unconfirmed transaction" really unconfirmed? If you still have problems with your full node, you may check that "unconfirmed transaction" on an online block explorer.  
> **username_2**: Pointing fingers at Coinbase or someone else cannot solve the problem. Theoritically, Coinbase could do the "child-pay-for-parent" (Electrum provides this feature directly to both sender and receiver, but it's more expensive than RBF however) trick to bump the fee, thus prioritising the stuck transaction. However, they might have their own wallet management policies which may sacrifice convenience and flexibility in exchange for security.  
> **username_2**: If coinbase provides a new depositing address to you, this should be totally fine, Coinbase guaranteed that "all addresses that have been generated for your account will remain associated with your account forever" here: https://support.coinbase.com/customer/en/portal/articles/2276500-why-did-my-wallet-address-change-  
> **username_0**: Blockchain.info doesn't recognize my hash. But my btc qt wallet is still debited. I'm upgrading now. And it's taking forever to sync. I know people don't like me criticizing coinbase but the day before there was no problem. I'm on my 15th day now. No result. No email or correspondence from them to eliviate my concerns or remedy they can offer. So I just want to make it aware to the crypto community about coinbase.  
> **username_0**: I will provide a bounty for anyone who can remedy this situation for me. I made the same offer to coinbase. No response though. Thank you.  
> **username_2**: You may lookup your address balance (and related transaction history) on an online block explorer. It sounds harsh, but, I don't think it's impossible - maybe your bitcoin wallet had already been compromised, thus your depositing transaction became an invalid double-spend which was discarded by the network, and, you didn't notice that because your full node had problem to sync.  
> **username_2**: Once you have confirmed your bitcoins are still on your own addresses, you can simply import the private key to other wallet (like Electrum) to send these coins to anywhere you want.  
> **username_0**: The day before this fiasco I made a transaction with coinbase. No problem. The next one, nothing. I can't even find the hash on blockchain.info. I am upgrading my node now and is taking forever to sync. It's been more than two weeks. What's the longest time a block sat in the mempool? I still want the transaction to go through. On the dread forum there is already complaints about coinbase. Now the cleaner can know.  
> **username_0**: Sorry clearnet*  
> **username_2**: Although most nodes (especially the ones used by mining pools) have a expiration time, there's no guarantee that an unconfirmed (0-conf) transaction will be forgot by every node. As long as the transaction is still valid, it's still possible for someone who didn't discard this transaction to rebroadcast it (or to directly include it in the block, for miners/mining pools).  
> **username_2**: Recently the mempool usually clears within one day. So, it's quite unusual for me that a transaction could wait for such a long period to confirm. You may copy the raw transaction from Bitcoin Core, then you can rebroadcast it with a block explorer like blockchain.info (or with the sendrawtransaction command). However, to ensure your wallet has not been compromised, you'd better check the balance and transaction history of your previous address on a block explorer. (you may do this with Tor browser to protect your privacy)  

---

### Answer by username_3 on 2019-10-20. Score: 0

It's not possible to remove your transmitted transaction from the network.

Even if you shut down and clean your own local client, other clients around the world have it in their mempool. That's why your local client reflects the balance minus the amount you sent, even though it's not confirmed. That's how it's supposed to work, Bitcoin TX's are supposed to be irreversible even before being mined.

So, Bitcoin does not have a TX revocation network message available.

Only thing you can do is, before this unwanted TX is confirmed, to use another client, which either didn't see your TX or allows you to craft TX's and broadcast them, to submit a new transaction containing a much higher fee and same UTXO's. (Double spending on purpose.)

This new TX will cost you the fee, but if you set your own address as beneficiary, the funds will return to your wallet and the old transaction will get discarded by the network as a double spend. This higher fee is your cost to revoke the old unwanted TX. All this has to be done before the old TX is confirmed in a block.

> **Comments:**
> **username_0**: Do you recommend a client/wallet that won't rebroadcast the tx? I don't want to be too much of a bother but could you refer a link so I can get back my satoshis. Any help would be appreciated. Thanks.  
> **username_3**: You can use Bitcoin Core itself to create a raw transaction. Then you send the funds to yourself using a bigger fee: https://stackoverflow.com/questions/38493893/heres-how-to-send-raw-transaction-btc-using-bitcoin-cli-command  
> **username_0**: Blockchain.info doesn't even recognize the hash. Can you explain why?  

---

