Some people who updated late were stuck in the wrong chain. To make sure that you are in the correct chain you can use the "getblockchaininfo" dash-cli command and compare the bestblockhash to any block explorer.
Thanks for that, yes, looks like I'm stuck on block 1091182, how can I fix this?
My first thought is to indeed use --reindex-chainstate
If that does not work you can try to have block 1091182 "reconsidered"
command in debug console : reconsiderblock hashfromblock1091182
to get the hash you can check block 1091182 in an (up to date and on the right chain) block explorer
Source (after a quick google search) : https://www.reddit.com/r/dashpay/comments/7ksem6/dashcore_refuses_to_synchronize_past_block_723541/