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
0100000001d30e6fdc3e10e6ef49d6c74c505db604e02b7f2767a682496a0e56198e77f080010000006a47304402206574a285a1ee4c8b306b09653366ccac7bf42316bfe1eb43d461805d0720d87e02204012af1e679097ac38121189824b570bdb3b0be0b45bf6520bfa61f76871c56701210263c6783e42877028cb1485de0a67027d410b096095ef55784b3ff0d51521b2dbffffffff02801a0600000000001976a91481d7d95c88d121322cf081f0b08fe85d09d7fea288ac85df0b00000000001976a9141e6b289a14b4565ec3d2e100e522ed3a6637bf2088ac00000000
more sites to push can be found here ->
https://en.bitcoin.it/wiki/Transaction_broadcastingI 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/9bf58adbbbe29d431679ee34e9a0a3042761685f5df4ced70041cd20eed70512Its 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/de8e6afd4e6d2a37ebd422421588f8a13cc52fa6a5b89299d8265517ed9c5371AFAIK 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