Transaction does not exist

[MaXeY]

Hello

i have 2 transactions for my friends, when i try to use Viabtc Transaction Accelerator it give me error "Transaction does not exist"

https://blockchain.info/tx/dd41c1fda8f1fb73952c54c324571fdfb7b39787859f4aba07a025d2e839f89d
https://blockchain.info/tx/6dfe30e74cf7f8b7a30507c54d00b9449b62364c81ff2fc80392c609dfdc9467

why am getting this error ?

[jackg]

Hello

i have 2 transactions for my friends, when i try to use Viabtc Transaction Accelerator it give me error "Transaction does not exist"

https://blockchain.info/tx/dd41c1fda8f1fb73952c54c324571fdfb7b39787859f4aba07a025d2e839f89d
https://blockchain.info/tx/6dfe30e74cf7f8b7a30507c54d00b9449b62364c81ff2fc80392c609dfdc9467

why am getting this error ?

I don't know why you're getting that error.
I tested it using my bitcoin client (electrum v2.6.3) and it seemed to verify the transaction for it's legitimacy.
Were these the origional tx's or the result of a double spend?
If it was just to friends, you could try cancelling the transaction and resending it. Or you can always contact quickseller on this forum or macbook-air an see if they can confirm it with their miners.

[Decoded]

Try to use it now. The viabtc node may have been lagging. Usually it is a matter of seconds to broadcast a transaction and get every node up to speed, but sometimes it can be a little longer. From the error message, what I think is happening is that viabtc's node has not logged your transaction in its mempool yet.

[Decoded]

Another thing - most nodes clear all transactions that have been pending for more than 24 hours.

When were the transactions broadcasted? A similar error is here - https://bitcointalk.org/index.php?topic=1803209.0

[MaXeY]

i made broadcast many times and success but when i tried to use VIABTC gives me error Transaction does not exist

[amaclin]

Another thing - most nodes clear all transactions that have been pending for more than 24 hours.

urban myth

[amaclin]

why am getting this error ?

because the transaction has dust output

[HI-TEC99]

I am actually having the same issue.

https://blockchain.info/tx/4e9a4b8f3d1990542de83bb44be67c295de516d608576fbd7bb89905715d3b83

I can't see this transaction on other blockchain explorer. I've tried to re-broadcast on blockchain.info an I am getting as error transaction already exist.

What can I do to resolve this issue.

Thank you very much

This is your transaction.

https://blockchain.info/tx/4e9a4b8f3d1990542de83bb44be67c295de516d608576fbd7bb89905715d3b83

It has this chain of unconfirmed input transactions. Each one must be confirmed before the next can confirm.

https://blockchain.info/tx/87d7697d0823d64a79ac560f8149c99b09271a3affc03cf260b902b01f4d126a

https://blockchain.info/tx/09be30034cc3bcea5ae0a477b68bb36146afac543fe794de96baf325ff79e572

https://blockchain.info/tx/338a7fcb22c05cf6059a4815da8269c955295036a8a91b65db8bfca9e92343b1

https://blockchain.info/tx/86fad64f047b9f1e0adc1935e441f73c970469bc3c95af6857d856bd5f0ea248

https://blockchain.info/tx/acaff5e5303a5888671727acd7c4267ff321401adf5ca86e9b69dc34a9b4c85f

https://blockchain.info/tx/3aae43110df607f1aff08ab7289695b87fe3e99d4a324f3684c4d33330f0b0e0

https://blockchain.info/tx/d20c079b178a97d105b6a993b29478e4aadff914fed22585e372a6bd027bbece

All those transactions lead back to this one. This transaction has a massive amount of small inputs all being sent as a total of 3.70325249 BTC to a single address. Fifty of those inputs were sent unconfirmed. Your transaction cannot confirm until this transaction confirms.

https://blockchain.info/tx/449083b66531b4a38188b255ee19c224264ead728467d2da254b8f0ebf453ce8

The first of those fifty unconfirmed inputs is itself part of a massive chain of unconfirmed inputs. I stopped counting its number of unconfirmed inputs at 47.

None of the other block explorers show those transactions, and none of them show any double spend transactions for the address that sent you coins (they all show it as never received coins or sent).

[sphibit]

Hi thanks for your reply.

So if I understand, it's normal that I can't find it on another blockchain explorer and just have to wait?

[HI-TEC99]

Hi thanks for your reply.

So if I understand, it's normal that I can't find it on another blockchain explorer and just have to wait?

You could wait and hope those transactions confirm, or pay a service like viabtc to confirm all those transactions for you. However there are possibly hundreds or thousands of unconfirmed transactions in the chains leading to yours. It might be expensive to pay to get them all confirmed.

We also provide manual accelerator service for special cases (dire urgency, extremely low transaction fee etc.) and require a donation of 0.01 BTC/KB for each transaction. Please contact support@viabtc.com for details.

Alternatively you could try contacting either quickseller or macbook-air and offering to pay them to get it confirmed. They can get F2pool to confirm specific transactions.

If you wait there is a danger the network might forget about those unconfirmed transactions, in which case you will never receive the money sent to you. It will return back to the wallet of whoever sent it to you.

That could happen fairly soon as the only block explorer that can see those transactions is blockchain.info. The network is already beginning to forget those transactions.

Those chains of unconfirmed transactions aren't normal. I would refuse to do business with whoever sent the coins in future.

[sphibit]

I have checked on viabtc and it says that the "transaction does not exist"

I'll try to send an email to  quickseller or macbook-air hope they can help to resolve

Thank you

p.s I've tried to broadcast on coinb.in and I've got this error  "Missing inputs"

[HI-TEC99]

If you pay someone to confirm it they might want a list of all the transaction IDs in the unconfirmed chain. Getting them all will require some work.

On this blockchain.info page showing your transaction click "Show scripts & coinbase" and the advanced view will open.

https://blockchain.info/tx/4e9a4b8f3d1990542de83bb44be67c295de516d608576fbd7bb89905715d3b83

The advanced view will indicate a transaction's unconfirmed input with a red letter U as shown here.



Click the link named "Output" that's to the right of the red letter U. That will take you to a new page showing the unconfirmed input transaction. The top link in that page is the transaction ID. For example your transaction's first unconfirmed input's transaction ID is this.

87d7697d0823d64a79ac560f8149c99b09271a3affc03cf260b902b01f4d126a

Copy and save that, then repeat the process by clicking the next red letter U to be taken to the next unconfirmed input's page. It will take some work to get to the end of the chain of unconfirmed inputs.

Did a service like blockchain.info send those coins?

[sphibit]

I send it through my cloud mining it's the first time i get this issue

[HI-TEC99]

I send it through my cloud mining it's the first time i get this issue

I'd complain to your cloud mining service. Sending transactions with so many unconfirmed inputs isn't acceptable. It can lead to is the possibility your transaction might never confirm.

[HCP]

I tracked it all the way back down about 5 of the chains of unconfirmed transactions from that massive transaction (449083b66531b4a38188b255ee19c224264ead728467d2da254b8f0ebf453ce8) to here: https://blockchain.info/tx/71a3a3a2e9c3d0a8863cf1bb258e8f9233caf5833b38a33d740e52a12f295ed4

They all seem to arrive at this same transaction after some truly ridiculous amount of unconfirmed transactions...

https://blockchain.info/tx/71a3a3a2e9c3d0a8863cf1bb258e8f9233caf5833b38a33d740e52a12f295ed4 did not appear to show on ANY other block explorers other than b.info, so the chances of it being mined were pretty low... so I have rebroadcast via my node and it now seems to be showing on b.info, blocktrail, btc.com and blockcypher.

the raw transaction, should you need it to broadcast it again, is:

Code:

0100000001e45514f33a40d3fad2f1aaf4954d4d9aab47335a55f7744dace2db724feeaf90010000006b483045022100c32194cfd68ad9afd8d31083f9f6c67adacb00770b3f8cdece86d9170ae7642002201849456adf4e6f3bd574eadf32b7fd49184d70ce62375dfc2fa934ea958cc321012103c36951beac30fd338333c523cd4400bdc0cf0f052aece1e9c2d28ba9731ff947ffffffff02942c0100000000001976a91493ff6a1722d952ea2e02b5455f152505910f0d4788acba929c11000000001976a914c74d1ff3dd2f13e71d2058956fd6129c919d7a0a88ac00000000

I've accelerated it using ViaBTC... and AntPool... so, hopefully, this will confirm soon... the fee isn't "great" but it isn't terrible either considering the current bitcoin network load. Once that one gets confirmed, then if b.info rebroadcasts the other transactions, they should slowly start confirming... otherwise use the "?format=hex" parameter to see the raw hex of all the unconfirmed transactions... and start rebroadcasting them

ie: https://blockchain.info/tx/<TRANSACTIONID>?format=hex

https://blockchain.info/tx/71a3a3a2e9c3d0a8863cf1bb258e8f9233caf5833b38a33d740e52a12f295ed4?format=hex

I doubt you'll find a miner to help... you're looking at easily 50-100 transactions that need to be confirmed before yours is somewhere near the top of the list!

EDIT: I've managed to rebroadcast a few transactions and they're slowly confirming... but it's going to take quite a while to get work through them all given the depth of unconfirmed parents... I suggest you contact the support of your cloud mining service and suggest they learn how "pay-to-many" batch transactions work...

[jackg]

I tracked it all the way back down about 5 of the chains of unconfirmed transactions from that massive transaction (449083b66531b4a38188b255ee19c224264ead728467d2da254b8f0ebf453ce8) to here: https://blockchain.info/tx/71a3a3a2e9c3d0a8863cf1bb258e8f9233caf5833b38a33d740e52a12f295ed4

They all seem to arrive at this same transaction after some truly ridiculous amount of unconfirmed transactions...

https://blockchain.info/tx/71a3a3a2e9c3d0a8863cf1bb258e8f9233caf5833b38a33d740e52a12f295ed4 did not appear to show on ANY other block explorers other than b.info, so the chances of it being mined were pretty low... so I have rebroadcast via my node and it now seems to be showing on b.info, blocktrail, btc.com and blockcypher.

the raw transaction, should you need it to broadcast it again, is:

Code:

0100000001e45514f33a40d3fad2f1aaf4954d4d9aab47335a55f7744dace2db724feeaf90010000006b483045022100c32194cfd68ad9afd8d31083f9f6c67adacb00770b3f8cdece86d9170ae7642002201849456adf4e6f3bd574eadf32b7fd49184d70ce62375dfc2fa934ea958cc321012103c36951beac30fd338333c523cd4400bdc0cf0f052aece1e9c2d28ba9731ff947ffffffff02942c0100000000001976a91493ff6a1722d952ea2e02b5455f152505910f0d4788acba929c11000000001976a914c74d1ff3dd2f13e71d2058956fd6129c919d7a0a88ac00000000

I've accelerated it using ViaBTC... and AntPool... so, hopefully, this will confirm soon... the fee isn't "great" but it isn't terrible either considering the current bitcoin network load. Once that one gets confirmed, then if b.info rebroadcasts the other transactions, they should slowly start confirming... otherwise use the "?format=hex" parameter to see the raw hex of all the unconfirmed transactions... and start rebroadcasting them ;)ie: https://blockchain.info/tx/<TRANSACTIONID>?format=hex
https://blockchain.info/tx/71a3a3a2e9c3d0a8863cf1bb258e8f9233caf5833b38a33d740e52a12f295ed4?format=hex

I doubt you'll find a miner to help... you're looking at easily 50-100 transactions that need to be confirmed before yours is somewhere near the top of the list!

EDIT: I've managed to rebroadcast a few transactions and they're slowly confirming... but it's going to take quite a while to get work through them all given the depth of unconfirmed parents... I suggest you contact the support of your cloud mining service and suggest they learn how "pay-to-many" batch transactions work...

If he can collate all of the TXs together, then it may be possible to contact a pool provider and see if they will confirm them all for you.
I'll try to make a list here of all of the TXs if I can.

Code:

Unconfirmed TXs:
1a27110592e9f12f76b02047dc9c7194d3a438bd5d2a850cf045d6d2a4c6d445
944d2d415c1b1ea785882d3292073e622b8387580cd6067215910e8aaf25d70e
a5665f526bd5977eadc11e6a885c6a352b7ba83bdf516cf66c9e434362a943c1
ffbc1bf4db5e75072a7aaa8f3cd186da4b9b0491966e1090fb15b0ceddcd1158
d3795f8093caa696d8c2cd0b09ee6968771884082dea9aab0a1b749436249d53
d33be0d50931cea88bb9c324b004dca387ff302a738e5c465d9d098ca17beda2
5ac3bfc9065da69a1fb811e4be6c17afb47810bf66e261a41fff9c7bfa18daaf
e670dd80a0d97c16fb37b5e6e117d139b47ffef3597bb2e98ded81c436f11970
167f91c47fb2251feae06cb4234fe19a99d597a64e4871530eb6ce48f0fa9fd2
7548703b1d9908b5edcacf671ecd91981e431fbbfa9be01fc8fd6167c9084052
e0c91e99588ee833c8fc71c0820a00548a556a3afcfcbaec5c91977f6f3602c6
da81149b08c995372d451bc4d52e2d2d5e90f2c69c316aa66226628a58ef9fa9
972e4aa83382e34e023033d2dd40cead43b19d090075592a05377f962894c1e3
cac85e9325150076db9a2f55305a822d14b0bd02256b4fd4562e927ecc4a4678
1166ea4be3c91ac10f33c7d452fe4a2fabb05dee0151ca103fcacc71eba507b7
64bd2443ad788db9bba4d2de0031af6921263b0279a3c79f4989803d9fca06dd
e47353f25fed34002e89ec0b67b8c12af70be4dcbef0b0efb48b54b509e3b1ef
13e1f4e4e574e59e32753c36cc87724206fe739513900680b95105ef6fb140b
d143733d6cd8c765b230655c75e1b9254f63fe1f6dd693be621a237817ddaf0b
f56dc641e1480f9454b1b69c5772716f9e941bd307e8f49f4a62d9f44e4fb230
bbe730149ead91123e7c69d7fd2823cf00c22d46b07cd1e10e0125a939c3d2d9
41ace46aeaea8c7d6fb19a0266aa4793276af0c2cf8448774b618b952ea6184d
231198ff4167a889981b39194f36879e19fda5ff954b13b1c502a557437dae5c
a32a577dd07270e820368c32e5602872e703a596986caad179cf5b4ce2fb1e6b

NOTE: THIS IS NOT ALL THE LIST, JUST THE START OF THE CHAIN.

If I'm honest, it looks like this is being used to obfuscate funds so they may be likely to scam or be doing something else illegal.

[HI-TEC99]

...If I'm honest, it looks like this is being used to obfuscate funds so they may be likely to scam or be doing something else illegal.

Either that, or they created a tree of too many unconfirmed transactions for a miner to accept.

The chain of unconfirmed transactions leads back to one with fifty unconfirmed inputs. The first input alone is part of a chain of over 47 unconfirmed transactions. If all fifty of those unconfirmed inputs are also parts of chains of over 47 unconfirmed transactions then the OPs transaction has a tree of 2350 unconfirmed transactions leading up to it.

A recent typical block contained 1867 transactions with total fees of 1.77800286 BTC. The OPs transaction tree might have too many unconfirmed transactions in it to fit into a block..

[HCP]

Seems they are slowly filtering through... I also noticed that it seems to be a big "web" rather than a tree...

A lot of the outputs from the earlier unconfirmed transactions, are actually inputs into that "giant" transaction: https://blockchain.info/tx/449083b66531b4a38188b255ee19c224264ead728467d2da254b8f0ebf453ce8

Quite a mess indeed... but they ARE slowly confirming... I've been rebroadcasting the "first" transaction after a group of unconfirmed transactions get mined... and it seems to rebroadcast the chain up to the max "mempool chain"... and that giant transaction now only has 15 unconfirmed inputs.

[HI-TEC99]

Seems they are slowly filtering through... I also noticed that it seems to be a big "web" rather than a tree...

A lot of the outputs from the earlier unconfirmed transactions, are actually inputs into that "giant" transaction: https://blockchain.info/tx/449083b66531b4a38188b255ee19c224264ead728467d2da254b8f0ebf453ce8

Quite a mess indeed... but they ARE slowly confirming... I've been rebroadcasting the "first" transaction after a group of unconfirmed transactions get mined... and it seems to rebroadcast the chain up to the max "mempool chain"... and that giant transaction now only has 15 unconfirmed inputs.

You are right, it's all due to you rebroadcasting through your node. I just tried broadcasting the giant transaction through coinb.in again and it gave the same "missing inputs" error as before. I doubt that transaction would stand a chance of confirming without your help.

[HCP]

Good news: https://blockchain.info/tx/4e9a4b8f3d1990542de83bb44be67c295de516d608576fbd7bb89905715d3b83 is now confirmed!

Bad news: it looks like the trail of unconfirmed transaction continues forward into infinity! Whatever cloud mining service that the "2nd OP" is using, is just creating a massive web/trail of unconfirmed transactions and making it really messy by occasionally paying themselves 0.0004 BTC every 5-10 transactions which they then use as inputs to "giant" consolidation transactions like this one: https://blockchain.info/tx/db559f692810302bad410deeba0557e33b579d6e8b3e00b8bdc8c7c88b4d6b67

Whether that is some sort of attempt to "scam" their users by ensuring the payments never get confirmed, or they're just incompetent I can't really say...