So, there are a good chunk of UTXOs that come from large transactions, e.g. look at the outpoint here – 3b791d360556423db6ba749899764b3276318cc3403c45a6ff4fc2e9e70862da:188
This is part of a transaction that is 50KB+. I was originally guessing that coinb.in was choking on decoding the large transactions, but that turned out to not be true. The real issue I think was that you were trying to make the transaction with a lot (if not all) of your UTXOs in one go, my script calculated you have:
2017/11/08 14:52:42 sweep_funds INFO Found 395 UTXOs on 1C5r7QJaQznPVxMCyBouWLCKDGPQ9dLiWN with a value of 7.82991871
That’s quite a lot of inputs to add to a single transaction (I calculated the transaction size would be roughly ~16KB unsigned) and, I’m guessing (and only guessing) that coinb.in was choking on this fact. Just as a test, I tried making a transaction with 15 of the larger inputs to see if coinb.in could decode it and it could:
2017/11/08 15:01:14 sweep_funds INFO Fetching transactions for 1C5r7QJaQznPVxMCyBouWLCKDGPQ9dLiWN .. this might take a while ...
2017/11/08 15:03:26 sweep_funds INFO Found 857 transactions
2017/11/08 15:03:32 sweep_funds INFO Found 395 UTXOs on 1C5r7QJaQznPVxMCyBouWLCKDGPQ9dLiWN with a value of 7.82991871
a4aaf3f186fe43012ec0a90ba56858206f92fb792052add46c863614c2c01da5:1141 -- 0.00126384
e0170b59c6a3c96b87841d89cbaa92c9f7bccbea7dd1893b45779a2d75358c55:1137 -- 0.00124916
ce614c01e2104f30c1ae27d896f6d2d0c5816a185a0759d71cd89f4abe4282ac:1138 -- 0.00122743
9410aeaf9855f62216a7c1056fb04c7b80ce0dd8d4208b335d538ed254b48d5c:1139 -- 0.00121117
a97cd0612c46033400def6a4a265c2f1897471efa2ef83584be7e2a57a641751:1133 -- 0.00119059
0bd524cafc6c5e1effbd0ba1497fbb0b380a3bdb622677e5261c4c6106a1a805:1131 -- 0.00114806
6c353202421ac7d4e91c4126b9ec3adc3ffee9b8bcac1dc70a121e07a6640168:1134 -- 0.00113921
020ce6e094a2933b1dd0569c756f546fef374b9fc797682b0261b024bd1db01b:1136 -- 0.00112942
7c8a7315eb5026dcd71e1e84166f119bb9339fab3cc4b8ac9cc5d2628154ddca:1143 -- 0.00111632
a78f7da21c9c0050c8f70bcd4e4e921ce9508b66456e8055725d40ab9d975c6b:1139 -- 0.00111049
b20bc545a34d70b20615ef2e9cb08a137e2080c520b4a6181d6c4878915af1c5:1135 -- 0.00110894
a1d4bd8fda17b8f2904191983b537ea5989b1560941d32686d40119e0b87c5b8:1141 -- 0.00109523
1ca317958e37580f75bf3c92f7f23d452e4b9a47c4f19713b9034c9048e39572:1128 -- 0.0010461
d9b25116a8310079148477e5d169a94ab4909017ea7b2c98e5c3fe3f152665f0:1286 -- 0.00060026
86b34ec55cfc5eaa23acfb8503fe974b4e58423eafe0e2e3bf4ba67eb5f770bd:1204 -- 0.0002581
2017/11/08 15:03:32 sweep_funds INFO
The above transaction uses those 15 UTXOs and spends it back to
1C5r7QJaQznPVxMCyBouWLCKDGPQ9dLiWN to create a ~2.2KB (when signed) tx with a 0.00033666 BTC miner fee-- note that you could sign this transaction and broadcast it, but you’d obviously be trusting me that the transaction does what I said it does (unless you decode it yourself with bitcoind or something like https://blockchain.info/decode-tx).
If you can expand on what it is you want to do and what your limitations are I could modify my script with some optional arguments to support your needs, some other people have had similar issues creating transactions with a large amount of UTXOs on the address with the script. Do you have a bitcoin core node? redeem.bitwatch can sometimes return spent outputs as unspent (edit: actually, this was probably the cause of your issue. I see that your address has some unconfirmed transactions and I know from past experiences that it takes a while for bitwatch to account for those).
What wallet are you using that won’t even let you create a transaction with some of your UTXOs until you consolidate it so that it’s fewer? If that is the only issue, and you just need to consolidate the many inputs into a fewer amount I suppose it wouldn’t be too bad to just create a few ~5-10KB transactions (reasonable enough, maybe could be larger). I could add some options that allow you to specify the amount of inputs to use for a transaction, or I suppose better yet would be able to specify a custom transaction (rough) size.
Also, I’m not sure why you’re using coinb.in to sign transactions but Bitcoin Core will happily sign even very large transactions without issue if you wanted to make one big transaction to consolidate all of the inputs at once, assuming that size would be < 100KB.