Drunk Stuck Tx

[nostar]

this pandemic is getting old. i did it again... day drank and thought i was being a smarty pants and tried transferring my FULL remaining core wallet amt to an exchange to, i don't know, sell the top? All I know is when i woke up the next day i had nothing in my wallet and nothing went through. it's stuck. i clearly see now what i did but my scotch eyes cleary didn't. can someone please explain to me cpfp and if, or how, i can do it in core? i am using 0.21.0. I do have a backup core wallet on an old linux box and am running that as it's the full node, not pruned like this one on my laptop.

this is what i have in core:

Status: 0/unconfirmed, in memory pool
Date: 2/16/21 14:26
To: xxxxxx
Debit: -xxxxxx sat
Tx fee: -540 sat
Net amt: -xxxxxx sat
tx id: xxxxxxxx
Tx total size: 1103 bytes
Tx virtual size: 540 bytes
Output index: 0

i might add that none of the block exp are finding the tx except blockchair and txfee dot org. also tried the accelerators and they all give me errors. idk.

thx. need to quit drinking. pandemic has gotten a hold of me.

[1714824554]

1714824554

[TryNinja]

It looks like you used a fee of 1 sat/vByte. Most explorers don't see your transaction simply because the mempool is so full that there isn't space for transactions under 2 sat/vByte anymore (the minimum was a lot more yesterday), so they just remove them. The ones you can find the tx are those that set a higher mempool maximum size.

Try taking a look at this thread: All about "stuck" transactions and what you can do to fix them

[nostar]

@TryNinja

yeah, i noticed that blunder.... i know exactly what my mind was thinking and it's making me nauseous right now. i'll take a look at this post. thx.

[nostar]

Try taking a look at this thread: All about "stuck" transactions and what you can do to fix them

money. i knew someone here could help. deleting the mempool.dat file, cause abandon tx was greyed out, worked for me. much appreciated. stay well.

[bitmover]

i might add that none of the block exp are finding the tx except blockchair and txfee dot org. also tried the accelerators and they all give me errors. idk.

thx. need to quit drinking. pandemic has gotten a hold of me.

As it shows in blockchair blockexplorer, you can try to broadcast it again.

Do you have the transaction HEX? (if you don't, I made a simple tool to get it here. It may work in your case)


You can just insert the transaction hex here:
https://blockchair.com/broadcast

And it will broadcast it again. It will show again in most blockexplorers after this, and it may get confirmed in a few days/weeks. This happened once to me a few weeks ago and rebroadcasting it solved the issue. Like suggested by achow101 here. You can also try to open your wallet again to rebroadcast it:

If you are incapable of performing any of the other options are are too afraid to do so, you can simply wait and hope that the transaction will eventually confirm. To make sure that network is constantly being reminded of the transaction, you can rebroadcast the transaction periodically. Most wallets will rebroadcast automatically, so simply leaving your wallet open will allow rebroadcasting to happen.

[TryNinja]

As it shows in blockchair blockexplorer, you can try to broadcast it again.

Wont do a lot when the fee is lower than what most nodes are asking for. Better to send the transaction with an actual fee for the current moment (1 sat/vByte is dead for now).

[bitmover]

As it shows in blockchair blockexplorer, you can try to broadcast it again.

Wont do a lot when the fee is lower than what most nodes are asking for. Better to send the transaction with an actual fee for the current moment (1 sat/vByte is dead for now).

If his transaction has no RBF enabled, that is all he can do... And it will get confirmed sometime if he keeps broadcasting it.

Fees may get lower in a few days/weeks. Yesterday you could get a confirmation with 7 sat/byte. Take a look here

https://blockchair.com/bitcoin/transactions?q=block_id(670809..670890),fee_per_kb(7000..8000)&s=id(asc),fee_per_kb(desc)#

[TryNinja]

If his transaction has no RBF enabled, that is all he can do... And it will get confirmed sometime if he keeps broadcasting it.

The issue was fixed already.

money. i knew someone here could help. deleting the mempool.dat file, cause abandon tx was greyed out, worked for me. much appreciated. stay well.

Once dropped, it's like the transaction never went through. Rebroadcasting it would only put him on the same spot he was before.

[nostar]

If his transaction has no RBF enabled, that is all he can do... And it will get confirmed sometime if he keeps broadcasting it.

Fees may get lower in a few days/weeks. Yesterday you could get a confirmation with 7 sat/byte. Take a look here

https://blockchair.com/bitcoin/transactions?q=block_id(670809..670890),fee_per_kb(7000..8000)&s=id(asc),fee_per_kb(desc)#

rbf was enabled however i wasn't aware that i needed to have actual btc in my wallet at the time i submitted the tx. i obviously thought dumping more into my wallet to cover a lower tx would suffice but no. lesson learned.

i f**king love bitcoin but sometimes it scares the s**t out of me. i think we're hunky dory. previous tx is abandoned and new tx w/ higher fee is in mempool. for some reason the hash isn't showing in any explorers but maybe that's because the abandoned tx is still lingering and thinks it's a double-spend attempt? idk. i'll sleep on it and see what happens tomorrow. i at least know how to get that abandon tx selection to work now as it's always greyed out for me. besides, not in a rush.

thx for helping though.

[Lordhermes]

If his transaction has no RBF enabled, that is all he can do... And it will get confirmed sometime if he keeps broadcasting it.

Fees may get lower in a few days/weeks. Yesterday you could get a confirmation with 7 sat/byte. Take a look here

https://blockchair.com/bitcoin/transactions?q=block_id(670809..670890),fee_per_kb(7000..8000)&s=id(asc),fee_per_kb(desc)#

rbf was enabled however i wasn't aware that i needed to have actual btc in my wallet at the time i submitted the tx. i obviously thought dumping more into my wallet to cover a lower tx would suffice but no. lesson learned.

i think we're hunky dory. previous tx is abandoned and new tx w/ higher fee is in mempool. for some reason the hash isn't showing in any explorers but maybe that's because the abandoned tx is still lingering and thinks it's a double-spend attempt?

If you have opted in for RBF for the transaction, it means you have attempted double-spending, therefore, miners find it hard to fasten such transactions. I will suggest you wait for the network to forget about the transaction for your transaction to be cancelled back since your fee is very low, then you can use sufficient tx fee next.

[nostar]

If you have opted in for RBF for the transaction, it means you have attempted double-spending, therefore, miners find it hard to fasten such transactions. I will suggest you wait for the network to forget about the transaction for your transaction to be cancelled back since your fee is very low, then you can use sufficient tx fee next.

i gave it a rest and completed my tx. all is well. love this community!