My transaction has been unconfirmed for over 12 hours because of low fees

hosseinimr93

legendary

Activity: 2380

Merit: 5213

Quote from: BitMaxz on June 13, 2021, 07:08:25 PM

Can you try to use "-zapwallettxes" to remove those unconfirmed transactions or to clear up your core wallet.

The zapwallettxes option has been removed from the latest version of bitcoin core. (Click here to see the reference.)

To radbulldog

It's possible that the address(es) you are trying to send bitcoin from has no balance at all. Maybe the outputs have been spent in another transaction and that's why your transaction wasn't broadcast even by your own node.

Is there any reason you are running a full node?
If you only want to make a transaction and you have valid unspent outputs in your wallet, you should be able to export your private keys from bitcoin core and import it into other wallets like electrum.

Note that if you use electrum, there's no need to download the blockchain.

For exporting your private keys from bitcoin core, you can use the following command.

Code:

dumpwallet

You can also use the following command to export private key of a specific address.

Code:

dumpprivkey

For importing your private key(s) into electrum, select "Import bitcoin addresses or private keys" when creating the wallet and enter your private keys.

Warning:
Download electrum only from its official website and do not forget to verify your download.

nc50lc

legendary

Activity: 2534

Merit: 6080

Self-proclaimed Genius

Quote from: radbulldog on June 14, 2021, 02:30:08 AM

Quote from: nc50lc on June 13, 2021, 10:41:22 PM

-snip-
Why? Guess you'll have to wait until it's finished since you've already started it.
Is your blockchain pruned?

No it was pruned to dump at 2GB by default now am downloading it fully hopefully prevent future troubles like this. Or is there a way to prune without the full download?

Ah, so that's why you've resync.
What I'm thinking is it might be not necessary depending on the cause of the issue.

But since resync is already initialized, there's nothing you can do but to finish it, and hopefully that might fix the issue.

radbulldog

newbie

Activity: 5

Merit: 0

Quote from: nc50lc on June 13, 2021, 10:41:22 PM

Quote from: HCP on June 13, 2021, 04:09:41 PM

Quote from: radbulldog on June 13, 2021, 03:39:20 PM

Status: 0/unconfirmed, not in memory pool

This is going to be a problem. It looks like your client has created the transaction, but it is only stored locally in your wallet file. It has not been broadcast (or it was rejected when your client attempted to broadcast it), nor is it in the mempool of your local node waiting to be broadcast. It's possible that it's been invalidated by inputs being used/double spent in other transactions.

In Bitcoin Core, if you goto the console ("Window -> Console") and use the following commands:

Code:

getrawtransaction 1d66b0f1a56e7b45c9390491513c39bdf2b3d2a76d346dfee919992c6dcfa835

If it's not in his mempool nor blockchain, but he's using the GUI (bitcoin-qt)
he can use right-click menu of the transaction in the 'transactions' tab and select "Copy raw transaction" to get the raw transaction.

But you're right, I think there's a bigger problem somewhere since the transaction wasn't broadcast.

Quote from: BitMaxz on June 13, 2021, 07:08:25 PM

Can you try to use "-zapwallettxes" to remove those unconfirmed transactions or to clear up your core wallet.

If it's not in his mempool, he can just abandon it, it's one of the options in the same right-click menu (clickable for "not in mempool" txns).

Quote from: radbulldog on June 13, 2021, 06:53:42 PM

I tried resync error so I'll reindex and start all over. Thanks

Why? Guess you'll have to wait until it's finished since you've already started it.
Is your blockchain pruned?

No it was pruned to dump at 2GB by default now am downloading it fully hopefully prevent future troubles like this. Or is there a way to prune without the full download?

nc50lc

legendary

Activity: 2534

Merit: 6080

Self-proclaimed Genius

Quote from: HCP on June 13, 2021, 04:09:41 PM

Quote from: radbulldog on June 13, 2021, 03:39:20 PM

Status: 0/unconfirmed, not in memory pool

This is going to be a problem. It looks like your client has created the transaction, but it is only stored locally in your wallet file. It has not been broadcast (or it was rejected when your client attempted to broadcast it), nor is it in the mempool of your local node waiting to be broadcast. It's possible that it's been invalidated by inputs being used/double spent in other transactions.

In Bitcoin Core, if you goto the console ("Window -> Console") and use the following commands:

Code:

getrawtransaction 1d66b0f1a56e7b45c9390491513c39bdf2b3d2a76d346dfee919992c6dcfa835

If it's not in his mempool nor blockchain, but he's using the GUI (bitcoin-qt)
he can use right-click menu of the transaction in the 'transactions' tab and select "Copy raw transaction" to get the raw transaction.

But you're right, I think there's a bigger problem somewhere since the transaction wasn't broadcast.

Quote from: BitMaxz on June 13, 2021, 07:08:25 PM

Can you try to use "-zapwallettxes" to remove those unconfirmed transactions or to clear up your core wallet.

If it's not in his mempool, he can just abandon it, it's one of the options in the same right-click menu (clickable for "not in mempool" txns).

Quote from: radbulldog on June 13, 2021, 06:53:42 PM

I tried resync error so I'll reindex and start all over. Thanks

Why? Guess you'll have to wait until it's finished since you've already started it.
Is your blockchain pruned?

radbulldog

newbie

Activity: 5

Merit: 0

Quote from: BitMaxz on June 13, 2021, 07:08:25 PM

Quote from: radbulldog on June 13, 2021, 06:53:42 PM

I tried resync error so I'll reindex and start all over. Thanks

Can you try to use "-zapwallettxes" to remove those unconfirmed transactions or to clear up your core wallet.

You can put that on the bitcoin core shortcut under properties>target put it at the end and then reopen the bitcoin core again.

It should be clear and the amount you sent recently should back to your balances. Now you can create another transaction this time make sure you are connected to the internet before you press the send button.

Thanks am already reindexing tbe entire core will see how it goes

BitMaxz

legendary

Activity: 3374

Merit: 3095

Playbet.io - Crypto Casino and Sportsbook

Quote from: radbulldog on June 13, 2021, 06:53:42 PM

I tried resync error so I'll reindex and start all over. Thanks

Can you try to use "-zapwallettxes" to remove those unconfirmed transactions or to clear up your core wallet.

You can put that on the bitcoin core shortcut under properties>target put it at the end and then reopen the bitcoin core again.

It should be clear and the amount you sent recently should back to your balances. Now you can create another transaction this time make sure you are connected to the internet before you press the send button.

radbulldog

newbie

Activity: 5

Merit: 0

I tried resync error so I'll reindex and start all over. Thanks

radbulldog

newbie

Activity: 5

Merit: 0

In Bitcoin Core, if you goto the console ("Window -> Console") and use the following commands:

Code:

getrawtransaction 1d66b0f1a56e7b45c9390491513c39bdf2b3d2a76d346dfee919992c6dcfa835

Just tried this and gotthis error message:

"No such mempool transaction. Use -txindex or provide a block hash to enable blockchain transaction queries. Use gettransaction for wallet transactions. (code -5)"

What should I do to proceed?

HCP

legendary

Activity: 2086

Merit: 4361

Quote from: radbulldog on June 13, 2021, 03:39:20 PM

Status: 0/unconfirmed, not in memory pool

This is going to be a problem. It looks like your client has created the transaction, but it is only stored locally in your wallet file. It has not been broadcast (or it was rejected when your client attempted to broadcast it), nor is it in the mempool of your local node waiting to be broadcast. It's possible that it's been invalidated by inputs being used/double spent in other transactions.

Did you receive some sort of error message when you attempted to send this transaction?

In Bitcoin Core, if you goto the console ("Window -> Console") and use the following commands:

Code:

getrawtransaction 1d66b0f1a56e7b45c9390491513c39bdf2b3d2a76d346dfee919992c6dcfa835

This should output a big long string of hex characters... then you want to use:

Code:

sendrawtransaction COPY/PASTE_THE_BIG_LONG_STRING_OF_HEX_CHARACTERS_HERE

What is the output from the sendrawtransaction command? Huh

radbulldog

newbie

Activity: 5

Merit: 0

Hello everyone, I do have a similar problem searched and Google led me here, the Thread all about "stuck" transactions says to ask miners to add transaction to pool. It's my first time and have 2 transactions that need help but this is more urgent.

Can someone please help me.

Transaction ID: 1d66b0f1a56e7b45c9390491513c39bdf2b3d2a76d346dfee919992c6dcfa835

Accardo

hero member

Activity: 1274

Merit: 561

Leading Crypto Sports Betting & Casino Platform

Quote from: Pmalek on June 13, 2021, 03:03:40 AM

The mempool looks pretty good right now and if your transaction is valid and got broadcasted correctly, I suggest you take another look at it as the problem has been probably solved already. At the moment of writing this post, there are less than 1.000 unconfirmed transactions in the mempool.

Thank you so much the transaction was confirmed yesterday.

Pmalek

legendary

Activity: 2730

Merit: 7065

The mempool looks pretty good right now and if your transaction is valid and got broadcasted correctly, I suggest you take another look at it as the problem has been probably solved already. At the moment of writing this post, there are less than 1.000 unconfirmed transactions in the mempool.

HCP

legendary

Activity: 2086

Merit: 4361

Quote from: Accardo on June 10, 2021, 05:01:16 AM

I traded some bitcoin yesterday with a fee of $0.88 and till now it is still unconfirmed what can i do? should i wait till eternity or will get confirmed soon?

How exactly were you trading bitcoin? Huh

Were you doing this "P2P" where you were directly sending coins to someone in exchange for payment or were you doing this on some sort of exchange? Huh

Quote from: Accardo on June 11, 2021, 02:10:37 AM

Seems the transaction has been forgotten.

Without the transactionID it is difficult to know exactly what is happening... but by "forgotten", do you mean that the transaction is no longer shown on block explorers or that it is just sitting there unconfirmed and has been "forgotten" by the miners? Huh

Or is it just not showing in the exchange system that you are using? Huh

I doubt a low fee transaction would have dropped been dropped by most nodes given the current state of the network... there are less than 50k unconfirmed transactions, mempool is ~200megs and fees are running at the 30 sats/byte level. So the network is hardly overloaded.

NeuroticFish

legendary

Activity: 3668

Merit: 6382

Looking for campaign manager? Contact icopress!

Quote from: LoyceV on June 11, 2021, 05:48:21 AM

Quote from: Accardo on June 11, 2021, 02:10:37 AM

Seems the transaction has been forgotten.

It doesn't make much sense though to drop this quickly when mempool isn't even full.

That's correct. The only scenarios that make sense to me and would make the transaction dropped this fast with current mempool state would be:
* the transaction was double spent (RBF)
* one of the parent transactions was unconfirmed and was double spent (RBF)

LoyceV

legendary

Activity: 3290

Merit: 16489

Thick-Skinned Gang Leader and Golden Feather 2021

Quote from: Accardo on June 11, 2021, 02:10:37 AM

Seems the transaction has been forgotten.

If it dropped out of mempool, the sender (you?) can just send it again with a higher fee. It doesn't make much sense though to drop this quickly when mempool isn't even full.

Accardo

hero member

Activity: 1274

Merit: 561

Leading Crypto Sports Betting & Casino Platform

Thank you everyone for the replies. I will wait though this Is another fresh day. Seems the transaction has been forgotten.

mocacinno

legendary

Activity: 3584

Merit: 5243

https://merel.mobi => buy facemasks with BTC/LTC

Quote from: sheenshane on June 10, 2021, 10:12:39 AM

--snip--
No, more or less it might 14 days if your transaction stuck due to the low fees, otherwise, if your transaction will be forgotten by the network it will return to the sender's wallet. --snip-- This because mempool has no limited space, based on my understanding it's only 300MB, once the capacity has been reached it will select new transactions that higher than the required amount of the mempool.
--snip--

It's worth telling that 14 days/300Mb are the default settings for a node...
Every node owner can add startup parameters (in this case maxmempool and mempoolexpiry). So it's not like every node will drop a stuck transaction after 14 days, or when the size of the mempool exceeds 300Mb... Some nodes have waaaay bigger mempools (both in size as in time), so even if 90% of the nodes have dropped a transaction, it might still end up in a block if a couple of miners did not run their node with default settings (which might make sense for them, it's all about the money, and the more transactions you keep in your mempool, the more beneficial blocks you can build).

It's not only the maxmempool (size) or the mempoolexpiry (days) that can be set, a node owner can also set things like maxorphantx, wether or not the mempool will persist after a restart, minimum relay fee,... (and those are just settings for the core implementation, other implementations might have even more settings).

Bottom line: when talking about mempool or tx relaying, it's very hard to talk in absolutes since there is no "main" mempool. "The" mempool is just thousands of people running their own node with their own settings keeping a bunch of unconfirmed transactions in memory.

sheenshane

legendary

Activity: 2492

Merit: 1232

Quote from: Accardo on June 10, 2021, 05:01:16 AM

..should i wait till eternity or will get confirmed soon?

No, more or less it might 14 days if your transaction stuck due to the low fees, otherwise, if your transaction will be forgotten by the network it will return to the sender's wallet. AFAIK, the node will automatically reject those lowest fee transactions in order for the node will accept those higher transactions. This because mempool has no limited space, based on my understanding it's only 300MB, once the capacity has been reached it will select new transactions that higher than the required amount of the mempool.

All said above was right, they explained it very well and I hope you understand now that paying a small fee will result of stuck transaction, always refer to https://mempool.emzy.de/ for the right transaction fee.

o_e_l_e_o

legendary

Activity: 2268

Merit: 18711

Quote from: mocacinno on June 10, 2021, 05:50:44 AM

So my initial advice still stands:

Absolutely. I was talking more in generalities and for moving forward. Too often, especially in these "my transaction is stuck" threads, we see people talk about fees in a flat fiat rate, which is the wrong way to think about fees. If they keep thinking about fees in this way, they will keep having issues.

It's like someone says "How much does gas cost?" and you say "Oh, about a gram of gold". A gram of gold per what? Liter? Gallon? Quart? And who pays for gas using gold? The correct answer is "Oh, about $3 per gallon".

Miners care about the amount of bitcoin per vbyte. Start thinking about this and you'll have fewer issues with fees in the future.

mocacinno

legendary

Activity: 3584

Merit: 5243

https://merel.mobi => buy facemasks with BTC/LTC

Quote from: o_e_l_e_o on June 10, 2021, 05:15:30 AM

Talking about fees in terms of a flat rate is meaningless, and talking about fees in terms of USD is equally meaningless.

Fees are paid in bitcoin, not fiat. The constant volatility of bitcoin means it is impossible to compare two or more fiat based fees. Further, appropriate fees depend entirely on the size of your transaction in terms of virtual bytes, not financial value. A transaction for $10 could take up 10,000 vbytes, whereas one for $1 million could take up 200 vbytes. An appropriate fee for one could be a gross over or under payment for the other.

You need to start thinking about fees in terms of sats/vbyte, and start using sites which suggest appropriate fees using these units such as https://mempool.space/

100% correct.
This being said, an 88 cent fee is ~2300 sats. Since a 1 input, 2 output tx is about ~220 bytes in size, it's safe to assume that (best case scenario) he payed a ~10 sat/vbyte fee.... Worst case a 1 sat/vbyte fee (otherwise the odds are pretty big the tx wouldn't have been relayed).

So, even best case scenario, he used a 10 sat/vbyte fee, whilst a 15 sat/vbyte fee is needed... So my initial advice still stands:

if it was opt-in rbf (we don't know this), he could bump the fee. This would speed up his tx irregardless if the actual fee was 1 sat/vbyte or 11 sat/vbyte... If he bumped it to > 15 sat/vbyte he'd have a decent chance of getting his tx confirmed
if he was the receiver or if he received change (we don't know this) he could do a cpfp. Same here, this would work irregardless of his initial fee, as long as the (child transaction's fee + stuck tx fee) / (size of the child tx + stuck tx) > 15 sat/vbyte this would work
if his feerate was over 10 sat/vbyte (we don't know this, but best case scenario this is possible), he could try the free viabtc tool. This would not work if his fee < 10 sat/vbyte tough
if he's willing to pay, a big mining pool (like viabtc) can always help him out. This would work irregardless of his initial fee... He just needs to pay them...
irregardless of his fee, waiting will either solve the problem, or the tx will eventually drop from the mempool of most nodes, so at least he can re-create his tx

rebroadcasting could potentially be good, but could also be a bad idear, depending on the actual fee and how you think the mempool will evolve in the short term.

Topic: My transaction has been unconfirmed for over 12 hours because of low fees (Read 403 times)