What happens when your BTC transaction gets “stuck”?
Got a transaction stuck in a pending state with little hope of getting confirmed soon? Let’s learn why this happens and how it can be fixed.
Transactions get stuck because the transaction fee you set was too small. A fee that’s “too low” simply means that miners are filling their blocks with other transactions that pay them higher fees. Unless transaction volumes decrease, your transaction may not get confirmed and the funds won’t reach their intended destination.
However, it should be noted that your funds are NEVER at risk of permanent loss when pending. They will either get confirmed eventually, or they’ll be “forgotten” by nodes after a certain period of time and you’ll regain access to them in your wallet.
In the meantime, you may have some options to speed up your transaction, depending on what features are offered by the wallet you used to send it. We’ll go through each of those options in this article.
Analyzing the Mempool: How to Determine a Good Transaction Fee
The mempool (short for “memory pool”) is a collection of pending transactions that have been validated by nodes but not yet confirmed (i.e. included in a block of the blockchain) by miners.
It is built into the network that transactions with too low of a fee will be rejected right away. In other words, nodes will not include the transaction in their mempool (aka memory pool) and it will not propagate to other nodes. At the time of writing, the minimum transaction fee required to enter the mempool is about 5 sat/vBtye (satoshis per vByte of data).
You can think of a transaction fee as paying for the block space that is consumed by your transaction. Block space is measured in vBytes. That’s why transaction fees in Bitcoin are not dependent on the amount of funds being transferred, but on the amount of data that needs to be included in the blockchain.
This chart helps you visualize how transaction fees can change over time. When demand for block space is high (i.e. high transaction volume), fees go up. Essentially, you as a user have to compete with other users to incentivize profit-driven miners to include your transaction in their block.
How Your Funds Eventually Return to You
As mentioned above, your transaction may eventually be “forgotten” if you set too low of a fee. This is because each node’s mempool is not infinite in space, but rather limited to 300MB in the typical node implementation. When the mempool reaches full capacity, nodes will typically get rid of the lowest fee transactions in order to add higher fee transactions. Once this occurs, the funds in your “forgotten” transaction become accessible to you again.
The graph below will help you to see how this happens in practice. On the left side of the graph, the mempool is clearing out regularly, meaning that even 1-2 sat/vByte transaction fees were sufficient if you were okay with waiting a while for confirmations. On the right side, however, your transaction will never even be included in the mempool if the fee is below 5-6 sat/vByte.
Your transaction can also be “forgotten” because of node restarts and mempool expiry times. On average, it takes a few days for this to occur and for you to regain access to your funds. However, it depends on transaction volumes and other variables, so it can sometimes take much longer.
For those cases, we’ll explain the other methods you can try for getting your transaction confirmed.
Trying to “Redo” the Transaction
What if you were to create a new transaction sending the same funds to the same destination but with a higher fee? Uh-oh... from the perspective of a node seeing the new transaction, you’ve just attempted a double-spend. When detected, nodes simply drop the newer transaction.
Bitcoin nodes follow a “first-seen” policy, which means that node software considers the first transaction they receive as valid, and any subsequent transaction they see attempting to spend the same coins will be considered invalid and will not propagate.
So, what options exist if a transaction is stuck in the mempool and you don’t want to wait for it to be confirmed or forgotten? Below are the most common solutions.
Opt-In Replace-by-Fee (RBF)
In 2016, a policy was proposed in BIP 125 to allow replacement transactions. It essentially enables you (ie. the sender) to notify nodes in advance when you want a transaction to be replaceable.
Let’s say you send a transaction and you’d like to be able to replace it in case you set the fee too low. If the RBF feature was enabled and the nodes implemented the RBF policy, you’re in luck. When the replacement transaction is sent to the nodes, they will replace the old transaction with the new one and broadcast it to their node peers.
Then miners will see the new, higher-fee transaction and they’re more likely to include it in a future block because they will earn more by doing so.
Remember, this can only be initiated by the sender. If you’re the receiver, you’ll want to look into a Child Pays for Parent transaction.
Child Pays for Parent (CPFP)
As we explained in our article about Taproot and Chain Analysis, UTXOs cannot be partially spent. Instead, they are always spent in full, but any leftover amount — called “change” — is just sent back to you as a fresh UTXO.
In a child pays for parent (CPFP) scenario, you can get your pending transaction confirmed by sending another transaction to yourself using the change from that pending transaction. You effectively create a “child” transaction to pay yourself the change but with a higher fee, as shown below.
Unlike an RBF transaction, a CPFP transaction can be initiated by any party receiving a UTXO in the parent transaction. In other words, either party A2 or B from the example above can use the funds they receive in the parent transaction to cover a higher transaction fee in a child transaction.
Here’s why it works for getting stuck transactions into a block. While miners would like to only include the child transaction because it has a higher fee, that isn’t possible. The child transaction is based on the unconfirmed parent transaction, so it’s only valid if the parent transaction is also on the blockchain. They become a package deal.
This means the cumulative transaction fees of the two transactions must be sufficient (in terms of sat/vByte) to get confirmed. In other words, the average of the two fees must be greater than the current fee level required to get a new transaction confirmed.
In practice, creating a CPFP transaction is much more difficult as it requires spending from an unconfirmed transaction, something that many wallets do not allow.
Transaction Accelerator Services
Finally, if RBF and CPFP aren’t options, you can try a more roundabout way of getting your transaction included in a block: a transaction accelerator.
This is a service offered by miners where they will take an external payment (e.g. using an altcoin, PayPal, or WeChat Pay) to include your transaction in one of their blocks. Basically, you provide adequate financial incentive to miners by paying them an extra fee on the side. We do not offer this service at Slush Pool, but a quick google search for “BTC transaction accelerator” will yield some results.
These external payments for transaction fees are known as “out-of-band” payments and they can potentially result in lower revenue for miners, so this is controversial. Stratum V2 brings greater transparency to out-of-band payments, as you can read about in this article from Deribit Insights.
Your Wallet Determines Your Options
It’s up to every wallet developer to choose which of the options described above they want to include for their users. For example, exchange wallets typically force a fixed fee no matter the amount being sent. That makes sense, as stuck transactions will inevitably create unhappy users and support headaches for them. Self-custody wallets (where you control your own keys) will often have more available options to boost a stuck transaction.
As a BTC user, you have the opportunity to be your own bank. That comes with many advantages including censorship and seizure resistance, but it also means that you can get into confusing situations like having a stuck transaction. We hope this article helped you understand what to do and how to prevent this from happening again in the future.
You can view the changelog also in our documentation.
See the full changelog
Get notified when we release new update
Wohoo! You're subscribed, we'll be in touch soon.
Something went wrong. Please try again.
this is a generic answer applying to "light" wallets - I don't know much about the blockchain.info-wallet
There are several approaches that may work. I'm not sure which methods are most easily available for a user of a blockchain.info-wallet, but probably #0a and #2, followed by #3, #0b and #1b.
0) Wait it out.
0a) Wait for the transaction to go through. Most likely there will be free capacity in the network after some hours, some days or a week. In periods with free capacity, even low-fee transactions will pass. Rarely one has to wait longer than the next Sunday evening.
0b) Wait for the transaction to be forgotten, and then create a new transaction with a higher fee. In some few exceptional cases (notably around new year 2017/2018 and in 2021) several weeks or even months have passed without any free capacity. The original transaction may eventually be forgotten by the network. Some wallets will then offer to create a new transaction, Mycelium will offer to delete the old transaction, and with some luck a "double spend" will be possible - though this is very unreliable as the original transaction may be purposely or accidentally rebroadcast both by the sender, receiver and any third-party.
0c) From some wallets, the most intuitive panic action is to actively rebroadcast the transaction. This probably won't help at all, and it's the exact opposite of 0b, so it's probably not a good idea
1) Double spend with a higher fee (RBF).
1a) Using the "Replace by Fee"-protocol - this probably does not apply to you, but it's arguably the best way to "unstick" transactions. If the original transaction is marked up with "RBF allowed", most of the network will accept a replacement transaction with a higher fee. Not all wallets supports setting this flag, and even fewer has RBF turned on by default - for a good reason, the RBF protocol allows an unconfirmed transaction to be reverted, so using the RBF-flag is a terrible idea if you want someone to trust a zero-conf transaction. (the RBF-feature has been removed from most Bitcoin Cash software, as they deem it both "harmful" and "not needed").
1b) Doing RBF/"Double spend" even if the original transaction was not marked as RBF. Miners (and nodes) are supposed to ignore the double spend transaction - but you may be lucky. You may need to use specialized software to perform such a double spend. It may work, either because the original transaction has ended up in a "ghost-like" state where it's known by some nodes but not others - maybe some miners are unaware that you're doing a double-spend - or it may work because some miners deliberately accepts double-spent transactions as they can earn more fees on it.
2) Child Pays for Parent (CPFP). if a new transaction is made with a high fee, building on top of the old transaction, most of the miners will include the whole chain of transaction in the block they're mining at.
2a) Get the receiver of the funds to spend the funds they received on a new transaction, with high fee. This may of course not always be possible, but ...
2b) If not all the money in the wallet was spent, the transaction will typically include two outputs, one "change UTXO" that goes back to the wallet. If you can spend this one with a higher fee, the transaction may go through faster. Some wallets have a menu option for "accelerating" the transaction through "CPFP". In some wallets one can manually decide what UTXOs to include in the transaction. One can also send all the funds in the wallet i.e. back to an address belonging to the same wallet, but the fee for that may become excessive as the wallet may be filled up with "dust" making such a transaction big and costly. Electrum does support spending some specific UTXO, and Mycelium has the "CPFP" acceleration button. If you can take out a backup seed phrase from your wallet, it can most likely be used in Electrum or Mycelium.
3) Ask the pools for help. viabtc has their "transaction accelerator" at https://pool.viabtc.com/tools/txaccelerator/, antpool.com also has some similar service, there even exists services where one can pay by credit card to get the transaction prioritized.
How to cancel a Bitcoin transaction if unconfirmed
A Bitcoin user can’t reverse a Bitcoin transaction after confirmation. However, they can cancel a transaction if unconfirmed. A Bitcoin transaction is unconfirmed if the blockchain doesn’t approve it within 24 hours. Miners must confirm every transaction via the mining process. For blockchain to approve a transaction fully, it must get at least three confirmations.
A Bitcoin transaction may remain unconfirmed for the following primary reasons:
- If it’s very recent, a user might have to wait longer to receive confirmation. Even the quickest network takes a minimum of 10 minutes to confirm a transaction.
- If the transaction fee was too low or not included, it might be unconfirmed. A simple rule that applies to Bitcoin transactions is that smaller amounts have lower chances of getting a successful confirmation.
Miners might not confirm transactions with too low fees. But if the network does not verify your transaction within 24 hours, you can do the following.
Reverse the Unconfirmed Transaction
You can reverse your Bitcoin transaction if unconfirmed within 24 hours. However, ensure that the transaction is genuinely unconfirmed. That means you have to wait for 24 hours. If you don’t get a confirmation within this time, use a reliable block explorer to confirm the status of your TX.
Since the blockchain is public, you can easily track your transaction. All you need is to enter the transaction ID to follow it with the block explorer. Every Bitcoin transaction requires at least three confirmations to be fully confirmed. If your transaction has two or one approval, you have to wait for a third miner to validate it. That’s because the validation process has already started.
Canceling a Bitcoin Transaction
If you don’t notice any confirmation, you can cancel your transaction.
Here’s how to do it:
- Use Replace by Fee or RBF Protocol
- Use Higher Fee Double Spend Transaction
With the RBF Protocol, you broadcast a Bitcoin transaction to the entire network for a second time but with a higher fee. That way, miners pick the transaction faster, thereby canceling the previous expenditure and creating a new one.
However, your Bitcoin wallet might not support RBF Protocol. Therefore, check whether your wallet allows you to do this first. You can select this option when sending out bitcoins to ensure that you can use it if necessary.
But if your wallet doesn’t allow you to use RBF Protocol, use the double-spend option. That means you create a new transaction with a similar amount. That means sending your Bitcoin transaction a second time with a higher fee.
How to Ensure the Confirmation of Your Transaction
Whether you receive Bitcoin from another user or a crypto exchange likebitcointrader2.com, your wallet should show this update automatically. Failure to confirm the transaction means you can spend the funds again from your wallet. However, this can take even a month. Nevertheless, you can avoid the problem of unconfirmed transactions.
For instance, you can use the suggested transaction fees suggestion option in your wallet. Changing the recommended amount or lowering it can hinder miners from confirming your transaction. In most cases, the wallet selects the fee a Bitcoin user pays miners automatically. And this reduces the waiting and confirmation hours for the transaction. So, if you don’t want your Bitcoins to remain stuck in the block for hours, don’t change the suggested transaction fees.
Blockchain creates a transaction whenever somebody sends Bitcoin. However, confirmation of every transaction involves complex mathematical calculations. Bitcoin transaction confirmation secures the network despite being time-consuming. The recipient gets their Bitcoin after blockchain makes an exchange a part of one block, and that’s how Bitcoin confirmation happens.
A Bitcoin transaction can fail to confirm, or become “stuck,” for many reasons. Stuck transactions may be confirmed after several days, but sometimes waiting isn’t an option. Fortunately, many stuck transactions can be cleared using nothing more than a Web browser. This article shows how.
The procedure described here should not be used by beginners trying to clear a stuck transaction of significant value. Doing so can lead to loss of money.
This article describes a practical technique for creating and clearing a stuck transaction, but using this technique effectively takes practice and understanding. To get the most out of it, consider following the article as written and only commit a trivial amount of money.
If any step describes a concept that doesn’t make sense, find a way to understand it. Leave a comment at the bottom of the article. Ask a knowledgeable friend. Post a question to BitcoinBeginners, Bitcoin Subreddit, or Bitcoin Stack Exchange. Whatever happens, be sure you understand, at a high level, the procedure described here before using it to clear a high-value transaction.
For demonstration purposes, this guide instructs you to enter a private key into a live Web form. An attacker can intercept this information and steal funds. Private keys should generally only be handled within a safe computing environment. However, given the small amounts of money involved in this demo, the risk is minor. A description of a more secure alternative appears before the conclusions to this post.
You can clear a stuck transaction with the method described here whenever you control one or more of its outputs. If you don’t control at least one output, the network won’t permit you to complete the necessary steps.
Fortunately, you will control at least one output in many situations. If you are the payee, then by definition you’ll control one output at least. However, even a payer controls one output in many transactions due to the need to collect change.
If your wallet supports child-pays-for-parent (CPFP), the method described here may be less convenient and secure. Similarly, if your wallet supports replace-by-fee (RBF), and you’ve marked a stuck transaction as replaceable, then the approach described here is likely to be more expensive and less secure than bumping the fee through your wallet.
In other words, use the method here when a transaction is stuck, you own at least one output, replace-by-fee is not an option, and your wallet doesn’t support child-pays-for-parent.
The most common reason for a stuck transaction is that it carries a fee that was set too low.
Bitcoin transaction fees can be difficult to understand because they touch on many concepts. An important number to keep in mind is your transaction’s fee density. Fee density (d) is calculated by dividing the transaction fee (f, in satoshis) by its size (s, in bytes):
d = f/s
In Bitcoin’s early days, fees represented a negligible fraction of miner revenue. Today, things are very different. Fees make up an increasingly large part of total revenue, so miners try to optimize the fees they collect from every block.
Pending transactions are selected by first sorting them in reverse order of fee density. The top transaction is removed from the list and added to a candidate block. This step is repeated until the block is full. At that point any remaining transactions will need to wait for the next block to become candidates for inclusion.
Most blocks are completely full today, meaning that some or even most transactions will be left behind. To a first approximation, miners don’t consider a transaction’s current wait time. This means that newer transactions can cut to the front of the line if they pay a higher fee density than yours.
The technique we’ll use to clear the stuck transaction is known as child-pays-for-parent (CPFP). Recall that Bitcoin is an electronic cash system in which users exchange value by transferring ownership of digital tokens. These tokens are called either “coins” or “outputs,” depending on context. A transaction mediates the transfer, which will remain incomplete for as long as a transaction remains stuck.
Fortunately, a miner will consider not only the fees of a pending transaction, but the fees carried by any children.
For example, imagine that Alice pays Bob 5 mBTC using a fee of 0.125 mBTC (12,500 satoshis). The transaction size is 250 bytes, yielding a fee density of 50 satoshis/byte. The market fee density, as determined by estimatefee.com, is 150 satoshis/byte. Bob’s inbound transaction is stuck because Alice’s fee is 1/3 of the competitive market fee.
Bob can clear the transaction by spending one of its outputs with a transaction that pays not only for itself (the child), but the original (the parent).
Imagine that Bob’s child transaction, like the parent, has a size of 250 bytes. The total size of parent and child is therefore 500 bytes. The total fee that must be paid by the child transaction can be found with the following equation:
fc = d×b - fp
where fc is the fee to be paid by the child, d is the current market fee density, b is the length of both transactions in bytes, and fp is the fee already paid by the parent.
The market fee density (d) is 150 satoshis/byte. The combined size of both transactions (b) is 500 bytes. The fee paid by Alice’s original transaction (fp) is 12,500 satoshis. Therefore, the fee that Bob’s child transaction must carry is 62,500 satoshis (150 satoshis/byte×500 bytes - 12,500 satoshis), or 0.625 mBTC. Bob publishes this transaction, causing both it and its parent to be confirmed in the next block.
The best time to learn how to clear a stuck transaction is before it becomes critical to do so. This section describes how to place a low-value transaction into limbo so that it can later be cleared. Users only interested in clearing a stuck transaction should read this section nevertheless because it discusses the tool that will be used to clear the stuck transaction.
Stuck transactions are easiest to create during times of high transaction volume. One way to determine if this condition holds is to use a fee monitoring tool such as estimatefee.com.
Begin by creating three paper wallets. The first will serve as a source, and the second will serve as a destination for a parent transaction with an uncompetitive fee density. The third will serve as the destination for a child transaction that pays for itself and its parent. This can be done by opening a browser tab and loading Bitaddress. Click the Paper Wallet tab and generate three unencrypted addresses without artwork.
First, route a ฿0.002 payment into the first wallet using a competitive fee. Wait for at least one confirmation.
Next, create a stuck transaction paying the second wallet from the first using the browser-based utility Coinb.in. Browse to the site, then select the Transaction option from the New menu. Into the first address field, paste the address of the first wallet, then click Load. Into the second address field, paste the address of the second wallet. Adjust the amount to yield a fee of 386 satoshis (฿0.00199614). Your signed transaction will have a size of about 193 bytes. Therefore, your fee corresponds to a density of about 2 satoshis/byte.
Click Submit when ready. Coinbin will present your unsigned transaction in hex-encoded form. Copy the text to the clipboard.
First, verify your transaction. Scroll to the top of the Coinbin page and click the Verify tab. Paste your clipboard’s contents into the text field and click Submit. Coinbin will show your transaction’s details. Pay close attention to the Outputs section. Ensure that the address matches your “Stuck Parent” wallet address, and that the amount matches your intended payment.
When satisfied with the unsigned transaction, sign it. Scroll to the top of the Coinbin page and click the Sign tab. Paste your raw transaction into the lower text box. Then copy and paste the private key from your wallet Deposit Address into the upper text field. Click Submit. Coinbin will generate a signed transaction in a new text field. Copy the text to your system clipboard.
Finally, publish your signed transaction. From the top of the Coinbin page, click the Broadcast tab. Paste your signed transaction into the text box and click Submit. Coinbin will display your transaction ID (“txid”) with which you can track the status of your transaction.
Use a block explorer such as Tradeblock to prove that your transaction is stuck (“Unconfirmed”). Paste your transaction ID into the text field at the top of the page. Tradeblock is especially useful because it shows the fee density under the heading “Fee/size” in satoshis/byte. Your transaction should have a fee density close to 2 satoshis/bytes. If things have gone according to plan, your transaction will remain unconfirmed for hours.
Use Coinbin to create a child transaction spending your unconfirmed stuck payment. The procedure is nearly identical to the one described above for creating a stuck parent transaction. From the New menu choose Transaction. Enter the address containing the stuck payment into the first text field, then click Load. Even though your transaction is unconfirmed, Coinbin should display the value of the pending payment. Enter the address that you’ll use to receive your unstuck payment in the second text field.
Choose a payment amount that leaves a fee large enough to pay for both the current transaction and its stuck parent. Use the formula introduced above to guide you:
fc = d×b - fp
For example, if both transactions contain one input and one output, their combined size (b) will be about 382 bytes (2×193 bytes). Your parent transaction already paid 382 satoshis (fp). If the market fee density is currently 141 satoshis/byte, then you’ll need to pay 53,480 satoshis, or 0.53480 mBTC.
Choose a payment amount that leaves an appropriate fee, then click Submit. You may receive a warning about a high fee. Click “OK, I’ve got it!” to continue. Coinbin will generate an unsigned transaction encoded in hex format. Copy it to your system clipboard.
Next, verify your transaction. From the top of the Coinbin page, select Verify. Paste your unsigned transaction into the text field.
After verifying your payment address and amount, sign your transaction. Click the Sign tab. Paste your unsigned transaction into the bottom text field. Into the top text field, paste the private key controlling your Stuck Parent wallet address. Be sure to use the correct private key; using the wrong private key won’t generate an error at this stage, but rather when you attempt to publish the transaction. Click Submit to sign the transaction. Copy the text from the field labeled “Signed transaction.”
Finally, publish your transaction. Click the Broadcast tab at the top of Coinbin. Paste your signed transaction into the text field. Click Submit. Coinbin will respond by displaying your new transaction (“txid”).
Use a block explorer to monitor the confirmation of child and parent. If all went well, both should confirm within the next block or two.
The above procedure has been tested and was found to work as described. Keep in mind, however, that fee densities will fluctuate over time — sometimes quite sharply. Fees reported here may be out-of-date when your transaction becomes stuck. Fee densities can even change during the time it takes to read this post. Be sure your child transaction pays a sufficiently high fee or it too will become stuck.
Nodes have limited capacity to store pending transactions. When no more space is available, transactions are evicted in reverse order of fee density. A parent transaction paying a very low fee may therefore not be available when you try to publish your child transaction. If that happens, you’ll need to re-publish your parent transaction in addition to publishing the child.
The above procedure exposes private keys on a network-connected computer. To avoid this unsafe practice, an alternative signing procedure can be used. It’s identical to the original, except that the signing step is performed on an offline computer.
Begin by creating an offline copy of Coinbin. Download the offline bundle by clicking on the “download” link at the bottom of the Coinbin about page. Save the archive file to a trustworthy removable medium.
To run Coinbin offline, boot into an offline session such as Tails. Open your removable medium and extract the Coinbin archive. Coinbin can be run offline by clicking on the file named in the folder.
Using this setup, transactions can be created online, saved to a removable medium, signed offline, then published online. To minimize the risk of obtaining a malicious copy of Coinbin that re-routes payments, transactions can be independently parsed and validated using a block explorer. For example, Blockchain and Blockcypher can decode and check a transaction before publication.
Clearing a stuck transaction isn’t difficult given the right tools and some practice. This article shows how using a procedure that only requires a Web browser. To recap, CPFP can be used to clear a stuck Bitcoin transaction using the following procedure:
- Obtain an address into which you’d like to collect the stuck payment.
- Find the market fee density using estimatefee.com.
- Compute the fee required to pay for both child and parent transactions using the formula fc = d×b - fp, where fc is the child transaction’s fee, d is the market fee density in satoshis/byte, b is the combined size of parent and child in bytes, and fp is the fee paid by the parent transaction.
- Create a child transaction that pays the fee you computed.
- Sign and publish the child transaction.
Yes, send me more helpful Bitcoin stuff like this
Bitcoin transaction stuck
Why transactions can take time to confirm
Wallets do not confirm transactions. The miners of each coin's network do.
The most common cause is making transactions with too low miner fees. While there are any transactions on the network paying miners higher fees, they have no incentive to confirm the ones paying them low fees. Too many transactions being sent worldwide can cause fees to increase, so low-fee transactions have to wait longer.
The second most common cause is having previous unconfirmed transactions. Generally transactions must confirm in order. New transactions usually can't confirm while there are other before it still unconfirmed. A transaction will confirm when there are no other transactions on the network paying miners higher fees.
How to prevent transactions from staying unconfirmed
The best way it to properly set the fees at the time of sending. Coinomi allows you to choose how much to pay for miner fees. For coins that give you the 3 dynamic options (low, normal, high), we recommend choosing the "high" priority fees for faster confirmation. Fee suggestions cannot predict the future, so may not be appropriate in case of a very sudden increase in congestion. You are always free to select the "custom" fee option and set the value yourself if you know which value to use.
How to make an unconfirmed transaction confirm faster
Incoming transaction: If you are receiving a transaction that is unconfirmed, your only option is to wait. Properly setting fees is responsibility of the sender. You may contact the sender to ask for higher fees to be used next time. The value of an incoming transaction will only count towards your balance after it confirms.
Ethereum: If you sent an unconfirmed Ethereum or token transaction, you can replace it with another transaction using higher fees. Step by step instructions can be found here.Making new Ethereum or token transactions without following the instructions will NOT make previous transactions confirm faster.
Bitcoin: If your Bitcoin transaction is unconfirmed, there are a number of services that claim to accelerate confirmations, for example https://bitaccelerate.com and https://pushtx.btc.com. Coinomi is not in any way affiliated with those services and cannot guarantee their efficacy. You can search for a trusted service that works best for you.
You can also check if the outgoing transaction on the blockchain explorer. If it has 2 recipients, it means that one of those is change returning to your wallet, and you can complete the steps below to make it confirm faster. This is a technique called "child pays for parent" (CPFP)
- Copy your own Coinomi BTC receive address
- Paste the copied address in the send screen
- Use the "max" button to send all funds
- Proceed to the confirmation screen and select HIGH priority fee or a custom value even higher
- Send and wait for the transaction to confirm
Other options like "Replace By Fee" (RBF) exist but currently aren't available in Coinomi and cannot be used.
How to cancel an unconfirmed transaction
Ethereum or token transactions: they can be canceled following the instructions here: https://coinomi.freshdesk.com/support/solutions/articles/29000009773.
Other coins: transactions of other coins cannot be canceled. Eventually they will confirm and successfully send the coins to the destination address. You can also open the wallet of the coin in Coinomi and at the top corner select "... / Resynchronize" once. If the unconfirmed transaction disappears, you can send it again with higher fees. If it doesn't disappear, try again the next day. This will only work for transactions that have been unconfirmed for weeks.
And when he finished he stroked his cock over Viola's lips. She mumbled something in her sleep, but did not react in any way. When I woke up the next day, I recalled the incident with shame, but.
- Scosche iphone cases
- Uf mobile pring
- Catchy stem titles
- Alpha x gtr
- Sol nectar
- Infinity cheer jacksonville
- Greige paint
Well, what, you take the girl as an apprentice. Natasha, Natasha, two rubles, and ours. Will you pay me extra for training a young specialist.