Right, but I can Darksend 7.289375 DRK to you, and I will get 2.710625 DRK change, and both of those amounts will be recorded in the blockchain. A timing analysis could trivially link the two addresses sending/receiving those two amounts that add to 10 DRK.
Evan is the right person to analyze how DarkSend will deal with timing analysis. Personally I had proposed a slide bar that can be used to increase the anonymity level by increasing the laundry depth (number of masternodes the transaction goes through) or/and the time depth of the transaction. I also remember that it was discussed on how there'll be multiple denominating pools like 0.1/1/10/100 etc which would break down even the smaller amounts to similarly sized transactions. I'm not sure what's the current state of development is in terms of laundry depth, batching transactions delay etc.
I don't think there's been an official statement about chained pooling being built into Darksend. AFAIK it's just an idea that was tossed around. Personally I think it's necessary for any usable level of anonymity (preferably with the ability to specify whitelisted masternodes).
In an older post of mine I raised a similar issue that if timing analysis can be performed then it's just a matter of time before an alternate blockchain explorer is made that will script-analyze the official and simply provide the "clean" output with certain probabilities.
Agreed. Which would reduce the anonymity of the Darkcoin blockchain to be on par with bitcoin's. I was asking the same questions a while back and never saw a satisfactory answer (unless I'm having a memory fail).
Btw, I got an idea just now: It would be an interesting twist if one could send to two addresses instead of one, in a single transaction, with the sent amount being broken into two randomly sized parts. For example I send you 16 DRK and you get 5.4 DRK in one address and 10.6 DRK in another. You still got 16 but it's in two addresses so noone can corelate my 16 output and your receiving of ..5.4 and 10.6. If a further layer is added (for practical purposes) to treat these addresses as one (for the sender and receiver) it could also be quite easy to use. Kind of meta-addresses that overlap/include the sending/receiving addresses.
ok -- but with a timing analysis, the number of transactions in (let's say) a 60 second window will be relatively few, so it's not too hard to reconstruct what really happened, especially with uncommon amounts (e.g. I send you 16.023957).