Unconfirmed transaction

[Khorasani73]

Hi i have an unconfirmed transaction can any one help me?

https://bitcoin.atomicwallet.io/tx/fdf585cbb52fb04e49cc637f6e359ea99cb07ed3692b74550772c033c7a72dac

[1715235127]

1715235127

[1715235127]

1715235127

[1715235127]

1715235127

[1715235127]

1715235127

[1715235127]

1715235127

[1715235127]

1715235127

[ranochigo]

Your transaction pays a transaction fee of 1 satoshi/byte. This puts it roughly at 22MB from the tip of the mempool, and each block shaves 1 MB of the tip of the mempool. It could take sometime before the transaction can be confirmed.

If you control the output address, you can do a CPFP by spending it with a higher fee to get it confirmed faster.

[Khorasani73]

No i cant do such those things you mentioned. So by waiting 72 hours it might be confirmed? I also have used this website to accelerate my transaction : https://bitaccelerate.com/
Does it have any results ?

[ranochigo]

So by waiting 72 hours it might be confirmed?

Depends on whether the mempool gets less congested or not. You can monitor https://jochen-hoenicke.de/queue/#0,24h and see if the 1sat/byte transactions are anywhere near 1MB.

I also have used this website to accelerate my transaction : https://bitaccelerate.com/
Does it have any results ?

No. It rebroadcasts[1] your transaction which shouldn't have any effect on your transaction unless it was poorly propagated which is not the case here.


[1] https://en.bitcoin.it/wiki/Transaction_accelerator

[Khorasani73]

thanks alot for guiding me and wish you bests in new year

[o_e_l_e_o]

It is not flagged as RBF, and you don't control the only output for CPFP, so there is very little you can do here. Further, the mempool is continuing to fill, and it will likely only get worse once the weekend is over, meaning that there is only a very small chance of confirming within the next few days. I think there is a good chance your transaction will not be confirmed before nodes start dropping it in a couple of weeks' time.

Your options are limited to:

• Ask the recipient to perform a CPFP
• Wait for it to drop, then make a new transaction with a larger fee
• Ask (and probably pay) a mining pool to prioritize it

[sheenshane]

No i cant do such those things you mentioned. So by waiting 72 hours it might be confirmed?

AFAIK, once it is unconfirmed due to the lowest fee, it will eventually be rejected by the Bitcoin network if your transaction is unluckily didn't accept.  It will approximately be estimated 1-7 days and back it your wallet.  So, next time if you are in hurry, you need to blindly accept the large fee or the fee recommended by the mempool.  I also suggest always use a Bitcoin Fee Calculator.


However, all suggestion above was right and if your wallet use for that transaction allows you to use this CBF or CPFP, then, there is a chance that your transaction might be boosted.  So far as of now, your transaction shows 0 confirmation.

[o_e_l_e_o]

AFAIK, once it is unconfirmed due to the lowest fee, it will eventually be rejected by the Bitcoin network if your transaction is unluckily didn't accept.  It will approximately be estimated 1-7 days and back it your wallet.

Not quite. The default mempool expiry, which is the time it takes for an unconfirmed transaction to be dropped from the mempool, is set at a default of 336 hours, which works out to exactly 14 days. Nodes are free to change this, but most don't. The only other way it would drop prior to this would be if the mempool hit its maximum size, which is set to a default of 300 MB, although again nodes can change this setting. Since the mempool is only sitting at around 20 MB, this is very unlikely.

As I said above, if waiting for the transaction to drop then he will be waiting a couple of weeks.

[bob123]

Unfortunately, since RBF is disabled and there is only one output, only the recipient can use CPFP to get it confirmed faster.
The history of the address you have posted lets me believe that it belongs to binance. In this case CPFP is not an option.

Using an accelerator doesn't work either, since the only one proven to work only accepts transactions with a fee of at least 10 sat/vB.

It seems like you'll have to wait. For the future, you might want consider to switch to a wallet where you can enable RBF and have full control over the fees.

[JohnnyBoyI]

Help - I am the recipient of a transfer that was never received from 2 years ago. It shows incoming to my Bitcoin Core Wallet but status is 0/unconfirmed and not in memory pool. The tx id does not show up on blockchain and other sites as if it does not exist. But again it shows incoming, is it possible sender sent transaction then double spent or completely low balled fee to void transaction? Wouldn't that still show a record of txid?? I have also been researching CPFP but cant figure out how to execute it in BC. Any ideas or Help would be greatly appreciated!

[LoyceV]

Help - I am the recipient of a transfer that was never received from 2 years ago. It shows incoming to my Bitcoin Core Wallet but status is 0/unconfirmed and not in memory pool. The tx id does not show up on blockchain and other sites as if it does not exist.

From my experience in similar cases: are you sure you're taking about a Bitcoin wallet? It could have been a wallet.dat that belongs to an altcoin.
Either way, after 2 years, chances are the inputs moved already so your transaction can't exist anymore.

[JohnnyBoyI]

Help - I am the recipient of a transfer that was never received from 2 years ago. It shows incoming to my Bitcoin Core Wallet but status is 0/unconfirmed and not in memory pool. The tx id does not show up on blockchain and other sites as if it does not exist.

From my experience in similar cases: are you sure you're taking about a Bitcoin wallet? It could have been a wallet.dat that belongs to an altcoin.
Either way, after 2 years, chances are the inputs moved already so your transaction can't exist anymore.

Thx for reply - The wallet.dat shows up in bitcoin core and lists the transaction, is it possible to still be an altcoin? Transaction details shows the value of transfer as BTC. I will look into altcoin.

[LoyceV]

The wallet.dat shows up in bitcoin core and lists the transaction, is it possible to still be an altcoin? Transaction details shows the value of transfer as BTC.

If it was originally in a Bitcoin Core data directory, it's most likely a Bitcoin wallet. The transaction didn't confirm for unknown reason, it could have been double spent, it could have just dropped out of mempool because of low (or zero) fee.

[Khorasani73]

Thank you all guys, my transaction got confirmed after 37 hrs.

[HCP]

Thx for reply - The wallet.dat shows up in bitcoin core and lists the transaction, is it possible to still be an altcoin? Transaction details shows the value of transfer as BTC. I will look into altcoin.

Yes, it is possible that the wallet.dat will still open in Bitcoin Core, even if it is an altcoin wallet.dat. They generally share the same file format. The "value of transfer" is simply a number in the wallet file and does not store the actual "unit"... so the "Core" wallet applications (ie. all the cloned altcoin wallets) will show that "value" in whatever currency the wallet has been set for.

To check, you can try and open a copy of the wallet.dat in a text editor and do a search for "name"... you should hopefully see some entries that look like cryptocurrency "Addresses"... if they do not start with "1", "3" or "bc1", then you're likely dealing with an altcoin wallet... like this example from a DOGE wallet.dat:


You can see all the "name" records start with a "D"

[bakasabo]

AFAIK, once it is unconfirmed due to the lowest fee, it will eventually be rejected by the Bitcoin network if your transaction is unluckily didn't accept.  It will approximately be estimated 1-7 days and back it your wallet.

Not quite. The default mempool expiry, which is the time it takes for an unconfirmed transaction to be dropped from the mempool, is set at a default of 336 hours, which works out to exactly 14 days.

As I said above, if waiting for the transaction to drop then he will be waiting a couple of weeks.

Hello o_e_l_e_o. Is it possible for transaction to be automatically resent back to mempool?

January 6 I've sent 0.0049 BTC (1291 bytes) with 2sat/b fee. I'm not in a rush, but it usually takes 2-4 days for transaction to be received. Hash ID was 2021-01-06, then I clearly remember it got changed to 2021-01-09, but not it is 2021-01-12 12:59. 0 confirmations all the time. 

Now I'm a bit worried as it looks like a roundabout of a long, zero confirmation transaction. I'm curious what should I do next except just waiting 

[o_e_l_e_o]

Is it possible for transaction to be automatically resent back to mempool?

Yes.

So I can still see your unconfirmed transaction on blockchair.com, with the initial broadcast time of 2021-01-06. It has never left blockchair.com's mempool.

However, if I look up your transaction on blockchain.com, as you say, it has a date of 2021-01-12. What has likely happened is that at some point it was dropped from blockchain.com's mempool, and blockchain.com then later re-received your transaction from another node and placed it back in to its mempool with the new time of arrival.

There is not much you can do except wait at the moment. The transaction is not opted in to RBF, and although you have a change output you could use to perform CPFP, the value on the change output is so small that you could probably only boost it to an equivalent of around 8 sats/vbyte, which would still leave you over 30 MB from the tip. The only real option would be to use CPFP, spending the change output as well as some other coins from that wallet to pay a much higher fee. If you are interested in this I can talk you through it, but it will not be cheap given both the size of your initial transaction and the fact you would need to boost up to around 100 sats/vbyte.

There is no need to worry, though. Your transaction will either confirm or be dropped completely and your coins will never leave your wallet. There is no risk of loss of funds.

[bakasabo]

There is no need to worry, though. Your transaction will either confirm or be dropped completely and your coins will never leave your wallet. There is no risk of loss of funds.

I require your help once again 

How to act on “ Transaction invalid: some outputs that it attempts to spend have been already spent or are no longer valid.”, its status has changed invalid and the amount sent added back to balance? I thought it has returned,   but in few hours it is send again automatically and again it has 0 confirmstion/unconfirmed.

[bob123]

How to act on “ Transaction invalid: some outputs that it attempts to spend have been already spent or are no longer valid.”

This means the transaction is invalid because the outputs do not exist (or are already spent).
Basically, you can not create that transaction with these UTXOs.

What wallet are you using? Is it fully synced?

its status has changed invalid and the amount sent added back to balance? I thought it has returned,   but in few hours it is send again automatically and again it has 0 confirmstion/unconfirmed.

I doubt the same transaction has been successfully broadcasted, since it is invalid 
What is the transaction id?

[HCP]

How to act on “ Transaction invalid: some outputs that it attempts to spend have been already spent or are no longer valid.”, its status has changed invalid and the amount sent added back to balance? I thought it has returned,   but in few hours it is send again automatically and again it has 0 confirmstion/unconfirmed.

Would need to see the transaction ID/details to get a proper understanding of what is truly happening... but the "Transaction invalid: some outputs that it attempts to spend have been already spent or are no longer valid" error generally occurs when you spend unconfirmed coins (ie. you're spending coins that were received in a transaction that was not yet confirmed) and then there is a "double-spend" or "RBF" executed on the parent transaction, which then invalidates that parent transaction... which in turn, invalidates the coins you're trying to spend in your child transaction.

More simply:

UnconfirmedParentTransactionA -> CoinsYou'reSpending -> UnconfirmedChildTransactionB

If UnconfirmedParentTransactionA is then invalidated by a double spend or RBF etc, then "CoinsYou'reSpending" no longer exist... so you can't spend them... and you get the error.


If it then sent a while later, without the error, it sounds like UnconfirmParentTransactionA may not have been double-spent/RBF'd. Instead it sounds like it might have just been removed from the mempool of the node you're trying to broadcast UnconfirmedChildTransactionB through. This would also have the effect of making "CoinsYou'reSpending" invalid, as the parent transaction no longer exists.

Then, someone rebroadcast UnconfirmedParentTransactionA, it was re-added to the mempool, "CoinsYou'reSpending" suddenly become valid again, and "UnconfirmedChildTransactionB" is suddenly "valid" again and able to be broadcast without error.