UPDATE: it turns out situation is quite different now... The chain is not stuck, it is forked. One fork is stuck at block 3882726, the other fork is at 3891268 and seems to be moving forward.
All my wallets are on the stuck fork, and the explorer is also on the fork stuck at 3882726.
See the excerpt from getpeerinfo result:
[
{
"id" : 2,
"addr" : "24.55.154.69:7695",
"subver" : "/Vault:3.0.1/",
"startingheight" : 3891268,
"synced_headers" : 3882720,
},
{
"id" : 3,
"addr" : "82.169.234.212:7695",
"subver" : "/Vault:3.0.1/",
"startingheight" : 3891268,
"synced_headers" : 3882720,
},
{
"id" : 4,
"addr" : "46.198.176.193:7695",
"subver" : "/Vault:3.0.1/",
"startingheight" : 3891268,
"synced_headers" : 3882720,
},
{
"id" : 5,
"addr" : "76.23.74.73:7695",
"subver" : "/Vault:3.0.1/",
"startingheight" : 3891268,
"synced_headers" : 3882720,
},
{
"id" : 6,
"addr" : "[2a01:4f9:4a:1d6e::2]:7695",
"subver" : "/Vault:3.0.1/",
"startingheight" : 3891268,
"synced_headers" : 3882720,
},
{
"id" : 7,
"addr" : "174.88.74.81:7695",
"subver" : "/Vault:3.0.1/",
"startingheight" : 3891268,
"synced_headers" : 3882720,
},
{
"id" : 8,
"addr" : "[2603:3011:e00:b600::d1e7]:7695",
"subver" : "/Vault:3.0.1/",
"startingheight" : 3891268,
"synced_headers" : 3882720,
},
{
"id" : 9,
"addr" : "82.21.164.47:7695",
"subver" : "/Vault:3.0.1/",
"startingheight" : 3891268,
"synced_headers" : 3882720,
},
{
"id" : 10,
"addr" : "95.217.77.209:7695",
"subver" : "/Vault:3.0.1/",
"startingheight" : 3891269,
"synced_headers" : 3882720,
},
{
"id" : 12,
"addr" : "73.121.220.52:7695",
"subver" : "/Vault:3.0.1/",
"startingheight" : 3891805,
"synced_headers" : 3882720,
}
]
So I wont be pushing the stuck fork now, as it makes little sense. Will resync my wallets to try and get to the longest fork.
Someone should probably contact CrtyptoID explorer owner to resync too.
Not sure which fork is CREX24 on.