Topic: "Transaction does not exist"? (Read 4130 times)

have you read the above post?

maybe Quickseller can also help you with this issue. no harm in trying, right?
https://bitcointalksearch.org/user/quickseller-358020

also, is it okay for you to post the tx hash, check where the problem is? usually, txs pending for weeks have used very low fee.

try entering your tx ID here also -

https://bitaccelerate.com/
https://www.viabtc.com/tools/txaccelerator
[/quote]

I have read it and I have message him but no reply yet.
Below is what I got from the transaction:

"  d2a6636744c8fa34d55bd2e816f9301ae504e862c0d07f3e07bb25c51049b73f: Pending/unconfirmed.
     in   [3045022100f43b97af7f00f9d9cfa9cae74f8c4dca6cd0af59e2d5c83275eeb234a5e1cad302205d90e2a1c8940efce8696f1d73f46d55ee124ffcca6c238d210652216214102201] [02465652a1902edc0e911d8c0fdc528ddd9929bb6c98474578bc4b0b6508afa07c]
          outpoint:7182a656a990f94bcb49ce5ae92e243639862b30f0c7e692260352839fc24b8c:184 hash160:fd798c1ff083b3cc50b1e0ad0929fcf6dd70077b
     in   [3045022100cbcc092dc2d203e4296b79b8b64856ad088d6d1dc4e2e7cb03a02ccde8e90a0e022029c3d634d5502788d15861187e6bd388d9d847f49b34a8cc1df0fca66b46ecbc01] [02465652a1902edc0e911d8c0fdc528ddd9929bb6c98474578bc4b0b6508afa07c]
          outpoint:1b08826dba9ca675e8ff388433baace6de00d9258b3e5ce8d1785066bebc2b79:24 hash160:fd798c1ff083b3cc50b1e0ad0929fcf6dd70077b
     in   [304402206359b97ac041742a3ebb1efb8e1180e1c6afbc79f7b57b5f2b1f1dd27cb522bf02201f8faf0a97feb25606ac07c47c99dd2fb989e43b50fbe9d777420bac439a16f401] [02465652a1902edc0e911d8c0fdc528ddd9929bb6c98474578bc4b0b6508afa07c]
          outpoint:8d24fa2f9c0d845729a70b3ada9fe6349b52cac95e1594ada6acc44a3748756e:84 hash160:fd798c1ff083b3cc50b1e0ad0929fcf6dd70077b
     in   [3045022100d5017437c8e7a81d8d08ad4d72ee4bfd595f573792a03f2263b70acb9afb09a302207765a56e3f5755ffb327484e1944685acac9470027ffb0dbcbe37ec69ff3604701] [02465652a1902edc0e911d8c0fdc528ddd9929bb6c98474578bc4b0b6508afa07c]
          outpoint:d01ed0d88c2efc66866e65355ba43dd62c73b8f58f71182f6f4b2d537a40dd30:1 hash160:fd798c1ff083b3cc50b1e0ad0929fcf6dd70077b
     in   [3044022070378f42aea8b7df7494cf76f7f8e66785f59f56f1f869ec92d694d2e0d75f43022035a50e9ac292382cd24bc129921278e4b0e51c7fa5dcefdd58de25791d02100a01] [02465652a1902edc0e911d8c0fdc528ddd9929bb6c98474578bc4b0b6508afa07c]
          outpoint:83ca94fccdf51695fabf15f07bd7f32a7c2d733d038e0a9f6d28d1f09e441472:0 hash160:fd798c1ff083b3cc50b1e0ad0929fcf6dd70077b
     in   [304402200bfa4e3bff9b23109a0d30a733d9fffcba1c6168adf37a2f63267335ac4d87cb022055aca9821029e9da0736d414bb582e7286f8571cba54b748ce53eee67699e78401] [02465652a1902edc0e911d8c0fdc528ddd9929bb6c98474578bc4b0b6508afa07c]
          outpoint:3b9747a7cc3b450711dbbb09166a67795a07681453746f18b5a6d7792025e3e1:81 hash160:fd798c1ff083b3cc50b1e0ad0929fcf6dd70077b
     in   [3044022054cf160a3c43283dfe074d3bed297894b88899396088f8f6f5adb27e83cb2c1502206db6cdc81549c72be1d1c9c3ad141a586821ec45484e7cada8c86843872181ab01] [02465652a1902edc0e911d8c0fdc528ddd9929bb6c98474578bc4b0b6508afa07c]
          outpoint:4442fbaaeb5008978b94ab8c67de646d94110f5fea9ce7be5ae6774f1d8cdf35:76 hash160:fd798c1ff083b3cc50b1e0ad0929fcf6dd70077b
     in   [3045022100b6dd908823e268ca3d6f13fa7e7be82d9057d795f97b9359be47a696b00f7a0e022076d65246c5b244777915ef832f32a90aaa04c91d5b3ab1fdea7d59079471530901] [02465652a1902edc0e911d8c0fdc528ddd9929bb6c98474578bc4b0b6508afa07c]
          outpoint:a39a8628d13679f3c33f5700bba57030bf5411dfd8e06d4159b70a04d51c656f:3 hash160:fd798c1ff083b3cc50b1e0ad0929fcf6dd70077b
     in   [304502210081bfe83969d75a4c1e769f9aaf179be87af0fad5ddf26ec6cab7afccffb421220220230136daeb55c90a7708dbd74e0039690d969bb481d3c96cef3673bca91cf3fe01] [02465652a1902edc0e911d8c0fdc528ddd9929bb6c98474578bc4b0b6508afa07c]
          outpoint:b64a779ecc7f3bcd11b6908e5d9ca95041c8c91a611a16408d3b923a767ffcd3:186 hash160:fd798c1ff083b3cc50b1e0ad0929fcf6dd70077b
     in   [3045022100fdccd73bd1ee1baf411b828f6d72842605d00b577c365c2ecbe9638123ba8c6502202b72b210f52008795e71504140de5ba069b81c0f0f7dbbf6a1f3e60099a4213901] [02465652a1902edc0e911d8c0fdc528ddd9929bb6c98474578bc4b0b6508afa07c]
          outpoint:a48a4c0b889731d613f4c17cd7d70fbb8398422a4572589c5ce7ea32ccfdbe0b:186 hash160:fd798c1ff083b3cc50b1e0ad0929fcf6dd70077b
     in   [3045022100f85b20f7e58c20dc580cb799e5c33487d270f5e5fd71e434618cb1f9bea1020c0220566cc85fded367dff933e2c796e8559006c5ef99c5b25548dd6f0d93d7170f3701] [02465652a1902edc0e911d8c0fdc528ddd9929bb6c98474578bc4b0b6508afa07c]
          outpoint:5f54909abaf58a5420ab25be28f77639e33b55c50ad2c31f366ddca13d50228f:69 hash160:fd798c1ff083b3cc50b1e0ad0929fcf6dd70077b
     out  HASH160 [85e38dc11579adf170450c2eb5782687741b9216] EQUAL 0.0212776 BTC"

How could resolve this. Thanks for any assistance.

It's hard to predict if mempools will get lower today.
I'll try to add it to viabtc's accelerator later (15minutes from now), I'll inform you if they accepted it.

As said above, please read my msg.

---

-previous post deleted + update-

Seems like the parent transaction was also unconfirmed and it has a much lower fee rate (25sat/vB),
that's what makes your transaction's fee rate irrelevant, miners are also considering the parent fee when prioritizing your txn.

So, I've requested viabtc to add the parent transaction instead, and it was mined by ViaBTC in block 654649.
Now I've just added your transaction:

Wait until ViaBTC mine a block or two. That's if spider failed to mine a block faster than ViaBTC.

---

-update-
It's now confirmed: 467c044f5aa5227e6ed4702072b9b332c40f6ef6541da261f523a06463493758 in block 654664.

Did you read the post right above yours?


Please move this question to a new topic... But i can give you some pointers: you payed 100 sat/byte while you should have payed at least double to have a decent chance of getting a confirmation in a semi-reasonable time.

Since RBF wasn't enabled, you can still do a cpfp or pay viabtc to include your tx into their next block (or try to get in their free accelerator service which only accepts 100 free submissions/hour). If you wait ~2 weeks, most nodes will have dropped your tx from their mempool, so shortly after 2 weeks, your funds should be "returned" to your wallet, depending on which wallet and which node it can take a little longer or a little shorter.

If you want an in-depth discussion about what you can do: open a new topic

Good morning
My transaction pending since 3 days.. Never waiting more than few minutes to maxim 3-4 hours
Dont have RBF enabled..or any other way to cancel/speedup the transaction
Any chances to uget confirmed today?  Or when will be the transaction "forgoten" and the money back?
https://blockchair.com/bitcoin/transaction/467c044f5aa5227e6ed4702072b9b332c40f6ef6541da261f523a06463493758

That transaction has 1NU1bTwCkV6mJ1qGNWUPanPA4Fgb5rBRkg as one of its outputs and I didn't receive an error msg.

It's now confirmed with 2 confirmations,
if you're receiving through a custodial wallet, you may have to wait till it has 6 confirmations (10 minutes per confirmation in average).

Next time, open a new thread when you need support, specially if it's off-topic to the OP.

Hi.

today i made a withdraw and receive a confirmation mail with a wrong link https://www.blockchain.com/en/btc/tx/013dc49cf90068a632eb9ce34c56dd6ca3d730d297f18a2833dc56ecc4b4112b

If you check the link online will show you an error.

And my btc never received in my destiny wallet 1NU1bTwCkV6mJ1qGNWUPanPA4Fgb5rBRkg

Please help me. Where is my btc?

This is most likely your issue. Multibit Classic is very old, outdated and has not been supported for a long time now. It was deprecated over 3 years ago (July 2017)!!?!

I would advise that you follow some of the guides available online for exporting your keys and importing them into Electrum. Refer here: https://github.com/Multibit-Legacy/multibit#next-steps-for-multibit-users

Once you have imported your keys into Electrum, you should be able to see your historical transactions/balances, and you should then be able to create/broadcast your transaction.


If you need any assistance, just ask.

have you read the above post?

maybe Quickseller can also help you with this issue. no harm in trying, right?
https://bitcointalksearch.org/user/quickseller-358020

also, is it okay for you to post the tx hash, check where the problem is? usually, txs pending for weeks have used very low fee.

try entering your tx ID here also -

https://bitaccelerate.com/
https://www.viabtc.com/tools/txaccelerator

Hi,
I have the same problem.
Tried to send from Multibit Classic 5.19 to Blockchain and it been pending/unconfirmed for 2 weeks.
Can I still get assistance in getting it confirm please. 

Thanks guys. Somehow the transaction is now confirmed. I will remember to keep an eye out, not to send "dust" as change back ty myself.

Some digging on your transaction:
http://mocacinno.com/feecheck.php?txid=d20483e4540ede66acacebfd1a50fca41d7b8749a163f95b2c5aea666429fad3

Allmost 2 Kb, a fee of 21 satoshi's per byte...

The raw transaction:

https://blockchain.info/tx/d20483e4540ede66acacebfd1a50fca41d7b8749a163f95b2c5aea666429fad3

It does indeed look like the change sent back to your change address can be considered dust by some nodes (800 satoshi's), so this might indeed be the reason for the rejection...


I find it strange that electrum created such a transaction having dust output...

Blocktrail's explorer says your transaction contains dust. I tried the viabtc accelerator but it's rejecting it like you say. The 0.00021229 BTC/KB fee is higher than viabtc's minimum required 0.0001BTC/KB. I don't know for sure why it's rejecting your transaction, but it might be because it contains dust.


https://www.blocktrail.com/BTC/tx/d20483e4540ede66acacebfd1a50fca41d7b8749a163f95b2c5aea666429fad3

If you are not in a hurry you could wait a long time for it to confirm, or if you want confirmation fast you could contact a bitcointalk user called Quickseller or another called macbook-air and offer to pay a small fee for them to get your transaction confirmed.

Both of them have access to the F2Pool mining pool's accelerator, and can get it confirmed in the next block F2Pool mines. Here's a review of QuickSeller's service.

I have the same problem.
My transaction https://blockchain.info/tx/d20483e4540ede66acacebfd1a50fca41d7b8749a163f95b2c5aea666429fad3 is stuck and shows in Electrum 2.8.2 as LOW FEE.
"Child pays for parent" option does not work.
Nor does ViaBTC transaction accelerator: "Transaction does not exist".
When I use https://blockchain.info/pushtx
I get the message: Error Parsing Transaction

What is going on?

Indeed, any stuck transactions need higher fees in order to be confirmed as soon as possible. Another is by means of waiting. There are instances that transactions took long time before it is confirmed. Especially if you put just a small amount of fee. And even if the transaction is sent, some encounters " Transaction does not exist" when pasting the blockchain Tx ID. But, that's normal. Just have to wait for some time and it will be confirmed.

Looks like you were able to get it confirmed.

Another method of confirming stuck transactions is to spend any coins sent to a change address in the stuck transaction with a higher fee.  This will entice miners to confirm both transactions.

Okay I did what you said but it says that the transaction already exists, but according to the ViaBTC accelerator it does not?

It says: Parse: Error Parsing Transaction .  What do I do?

Paste the raw transaction here:
https://blockchain.info/pushtx

Bitcoin Client Software and Version Number: Blockchain.info v1.11.11
Operating System: Windows 7 64-bit
System Hardware Specs: N/A
Description of Problem: I received a transaction several hours ago and it still has not confirmed. It also says the transaction does not exist when using the ViaBTC accelerator. How long do I have to wait/fix this?
Any Related Addresses: 1FRH94aiqeux42tcC4xNRZLMKwLau3x359 and 1BPQi19jJqnguurHU13BCYM2C6RkXG4NbV
Any Related Transaction IDs: 78b74ea1aa213017b190e694180a7147695257077b508c8a69b7f1df6e50ca10
Screenshot of the problem: N/A
Log Files from the Bitcoin Client: N/A