how's that possible?
where did it go?
As written in the linked article, the chain was forked.
This means that the problem doesn't "exist" on this blockchain.
The problem existed on an alternate blockchain until block 74691, then the correct blockchain/fork took over and the other blockchain/fork was dropped.