Need help

[rajat08]

@QS yeah, Im missing inputs as well, I assume one TX along the line didnt meet the criteria to get relayed because of a low fee. That way its easy to start such a chain.

Thanks shorena.
And my last question is what happens if the transaction didn't get confirmed.
What will happen to the bitcoins in those transaction?

When I get the ans of this I will lock this thread.

As long as the network knows about the transaction (or rather the entire chain) the bitcoin are stuck. Once a single TX in the long chain is forgotten, all following transactions are invalid. It would be like it never happened. Keep the thread open though. Id like to know what happens and maybe someone is willing to follow the chain to its source. If we can find the single TX with low fee we can rebroadcast that it might get the entire chain to confirm.

Ok I will Not lock the thread.

[mexxer-2]

What if that doesn't happen??

What will happen to the bitcoins in those transaction?

And Thanks for such fast reply BTW.

They will return to the sender.If it happens to the first tx of the chain transactions, its something like the network forgot the tx and all the other tx will be rendered invalid(as said by shorena).
AFAIK TX drop out of the network after 48 hrs of inactivity(if not rebroadcasted).
Correct me if I'm wrong

[shorena]

What if that doesn't happen??

What will happen to the bitcoins in those transaction?

And Thanks for such fast reply BTW.

They will return to the sender.If it happens to the first tx of the chain transactions, its something like the network forgot the tx and all the other tx will be rendered invalid(as said by shorena).
AFAIK TX drop out of the network after 48 hrs of inactivity(if not rebroadcasted).
Correct me if I'm wrong

There is no fixed time. If the node is not rebooted the mempool just gets bigger and bigger until it crashes. Its probably time for me soon. This will be patched with 0.12. btw.

[rajat08]

So many technical terms being used here. I have no idea about it.
All I care about is BTC 

I am only newbie in this thread.Why are such type of system made so complicated?

[Quickseller]

Ok I have Pm shorena & quickseller. Thanks mate for your help.

Append '?format=hex' at the end of tx link in blockchain(.info) and then copy the hex here: https://blockchain.info/pushtx and push the transaction

here is the raw tx

Code:

0100000001d30e6fdc3e10e6ef49d6c74c505db604e02b7f2767a682496a0e56198e77f080010000006a47304402206574a285a1ee4c8b306b09653366ccac7bf42316bfe1eb43d461805d0720d87e02204012af1e679097ac38121189824b570bdb3b0be0b45bf6520bfa61f76871c56701210263c6783e42877028cb1485de0a67027d410b096095ef55784b3ff0d51521b2dbffffffff02801a0600000000001976a91481d7d95c88d121322cf081f0b08fe85d09d7fea288ac85df0b00000000001976a9141e6b289a14b4565ec3d2e100e522ed3a6637bf2088ac00000000

more sites to push can be found here -> https://en.bitcoin.it/wiki/Transaction_broadcasting

I dont think it will help in this case. There is a very long (>>400) chain of unconfirmed transactions.

I stopped following the unconfirmed inputs after this one -> https://blockchain.info/de/tx/9bf58adbbbe29d431679ee34e9a0a3042761685f5df4ced70041cd20eed70512

Its either some script that isnt working properly to someone attacked a site (e.g. the Ponzi OP awaits a payout from) that works on unconfirmed transactions.

I don't think the child transactions have even been "seen" by the majority of the network, as when I attempted to broadcast the OP's transaction with my node, I received an error saying that there are missing inputs.

In order for the OP to have his tx confirmed, he will first need the first dependent transaction to confirm and then all of the child transaction will most likely need to be broadcast to the network.  

What if that doesn't happen??

What will happen to the bitcoins in those transaction?

And Thanks for such fast reply BTW.

If it does not happen then the transaction will never confirm. There is an obvious pattern in the transactions, so I would be willing to say they were most likely all sent by the same person/entity. I am still making my way back, however so far there are more then 700 dependent transactions.

I am running into quota issues with bc.i however the earliest transaction that I have found is https://blockchain.info/tx/de8e6afd4e6d2a37ebd422421588f8a13cc52fa6a5b89299d8265517ed9c5371

AFAIK TX drop out of the network after 48 hrs of inactivity(if not rebroadcasted).Correct me if I'm wrong

It depends on the blockexplorer that you are using, and on the mempool of the various nodes. Most block explorers (their nodes) will probably not even accept the transactions in this transaction tree, so they will never show up unless they get confirmed.

I would not be surprised if most of the transactions in the tree could get double spent as of now. For example de8e6afd4e6d2a37ebd422421588f8a13cc52fa6a5b89299d8265517ed9c5371 has inputs from 1B7mNTmT3YNv4TpdGGWEkbwwRQf7s66Zz9 and 19DuC9qnLJwXSCfLEnYEjGnRtEUWovqzbq with 1B7...Zz9 being confirmed. The person who controls the private keys to 1B7...Zz9 would probably not have any problems getting a conflicting transaction to broadcast and be seen by the network

[Quickseller]

I am not 100% sure about this, however it appears that all of the transactions in question might be dependent on 8707d8bb014aa249ead5a941a9ca6986d1599d533e22fa0c06d9ac3b26ef2f56 confirming, which is impossible because it appears to have been double spent by 3379184d3075f59d89f882de06c6cf3aa68a53e69c2653ccb5107dc2683351e2 a long time ago.

The double spend was confirmed in a block mined by AntPool and was not previously seen by blockchain.info's node prior to it being included in the block

edit:

I do know for sure that 291945338f98046581f8892722d6775aada4c8a9274bb7cf4cd0ac8b5f842215 is a parent transaction in the tree of unconfirmed transactions, and that it is the earliest transaction that I am certain the other transactions are dependent on.