Any examples of the "10 minute script" that's a theoretical danger in 2mb blocks?

On the bitcoin.org Capacity Increases FAQ, it states that one of the reasons not to have larger blocks is that

it’s possible to construct a transaction that takes up almost 1MB of space and which takes 30 seconds or more to validate on a modern computer (blocks containing such transactions have been mined). In 2MB blocks, a 2MB transaction can be constructed that may take over 10 minutes to validate which opens up dangerous denial-of-service attack vectors. Other lines of code would need to be changed to prevent these problems.

Does anyone know more about this?

Specifically, is there any examples of a single 1mb transaction that takes 30 seconds (or an example 2mb transaction). The FAQ says transactions like these have been mined. Does anyone have any links to those transactions for examination?

I'm trying to understand how a transaction can be so complex that it could do this, like how many inputs it would take, how many outputs, what sized fee it would require, etc.

Next time XT does large block testing on the TestNet, would anyone be able to use that to test a large script like this?

Seems like it's an opportunity to profile the processing subroutines to figure out optimizations and test simple mempool policies to prevent this from occurring.

Submitted December 31, 2015 at 08:18AM by DeftNerd http://bit.ly/1mSNrGy