Quote from: alifrenstein on November 10, 2017, 10:42:27 AM

Quote from: HCP on November 10, 2017, 10:38:29 AM

Quote from: alifrenstein on November 10, 2017, 08:26:37 AM

And here is the information that I get from Block.io when retrieving private keys for address 3CdYdQcc79QywRbZsAToKJx3AC83GGr1Ke :

* Address: 3CdYdQcc79QywRbZsAToKJx3AC83GGr1Ke
* Address Type: P2WSH-over-P2SH

Ohhhhh... it's a SegWit address... OK, all bets are off. I honestly have no idea what you need to do at this point... but that probably explains the "witness program does not match script hash" error...

As far as I can tell, I *think* that there are inputs used in your original transaction that are no longer available (ie. they've been spent in different transactions)... so I don't think your original transaction will ever confirm. It would appear that someone (your wallet? block.io? the receiving wallet? some other 3rd party?) is trying to rebroadcast that original transaction.

Give it a day or so... and it should all settle down and the transaction should be completely dropped from the mempool and your wallet should show you the coins etc.

Ok, but it's 4 days already. Only yesterday early morning I had a chance to send another transaction with a high priority from my Block.io wallet, but I missed that chance as I didn't expect the transaction to rebroadcast again. Anyway, so how can I access my Block.io wallet funds using the Private Keys? I still didn't find a way. There must be a solution to this and I hope that someone can help me. And by the way, there is still no answer from Block.io support. Sad

Look, you have created a very complex transaction and it has been pointed out that at least one part has an error.

Do this. Send a smaller amount of coin - pick the amount so that you get maybe 30 inputs to it. Or 60, whatever. Get that done. Then do another one.

In other words, break the problem into pieces, and handle each piece one by one. At the end you may only be left with one problematic input.