Basically any transactions you do happen in the current block, and are confirmed in the next block. This means if you send MEOW to a friend in block 10,003 then it won't be "official" until block 10,004 has been written (and propagated across the network i.e. X confirmations). If a multipool comes in while diff is low (which they tend to do) they "trick" the algorithm that calculates the next difficulty rating (for MEOW this happens every 120 blocks right now) and make it super high. The multipool leaves, the diff is high, and instead of the ideal time of 30 seconds (for MEOW) per block, it sets up to be much longer (maybe 10+ minutes). If your interaction with the system happens during these "slow block" periods then you get stuck waiting for blocks to be solved before your transfer is official.
This is the risk I was talking about 1 or 2 weeks ago already, when MEOW wasn't on cryptsy or coinwarz. That wasn't really hard to guess, every single coin on cryptsy/coinwarz has this problem right now, even those with a much shorter diff retarget, or even a retarget at each block (but not with KGW).
Too bad the next fork does not have the KGW, because it will really need it. Currently diff is jumping between 10.26 and 41.041 because of the 4x max factor.
These past few days, we're only getting 700 blocks per day instead of 2880. So the fork will not happen before 11 or 12 days. Because of this situation, I'm pretty sure the dev will change their plan, as leaf's dev's did, and other coin dev's also did.
If you guys don't know. Here is the dev's twitter.