Orphans happen frequently. It's expected and a part of normal bitcoin operation.
That particular block was replaced by this block:
https://blockchain.info/block-index/460156/000000000000000011b56fc32434c44bfa911c2cb148f1bf4328a1b65b5edaebMost (maybe all?) of those transactions from the block that you posted have already confirmed in other blocks. Unfortunately due to some bugs in the programming at the blockchain.info website, they don't always handle orphaned blocks very well and so their site will show transactions from orphaned blocks as unconfirmed even if they are actually confirmed in some other block.
If there is a particular transaction you are checking on, then take a look at it on some other block explorer such as blockr.io or blockexplorer.com. You'll almost certainly find that the transaction is confirmed and has been for many blocks.
lol, just decided to check that in my log:
2014-09-02 02:04:39 Requesting block 000000000000000011b56fc32434c44bfa911c2cb148f1bf4328a1b65b5edaeb peer=135
2014-09-02 02:04:39 Requesting block 000000000000000001602493a0776fddc7b785256fbdebcf92bf7b6bca9c06c6 peer=100
2014-09-02 02:04:40 UpdateTip: new best=000000000000000001602493a0776fddc7b785256fbdebcf92bf7b6bca9c06c6 height=318677 log2_work=80.473837 tx=45804592 date=2014-09-02 02:04:39 progress=1.000000
2014-09-02 02:04:40 received block 000000000000000001602493a0776fddc7b785256fbdebcf92bf7b6bca9c06c6
2014-09-02 02:04:41 received block 000000000000000011b56fc32434c44bfa911c2cb148f1bf4328a1b65b5edaeb
shame that blockchain.info only keeps the IP data around for an hour or two, i'm curious as to what the breakdown was % wise for the IPs it was connected to
my guess is it was probably orphaned since it was 250kb larger
