At the end the majority followed
@Spectral's chain, decided by fox. The fork is 5 blocks long.
The correct fork is:
#7723323 "block_id": "0075d93bb451648e59bd321cecccbeeb02000bcf" "spectral"
#7723324 "block_id": "0075d93c6b1f4691052a6b14e91f0561468506ac" "roadscape"
#7723325 "block_id": "0075d93ddd8ae094fb6b55d1b19b4bf342e97e2e" "delegate-clayop"
#7723326 "block_id": "0075d93e5fcd8a8a29c9c4b7720bf6c76c5b4024" "abc123"
#7723327 "block_id": "0075d93ff891fa5926ed57731ea7b62954885454" "bue"
#7723328 "block_id": "0075d9407ba9fb540c2515571330d308d3ab3837" "fox"
No idea why verbaltech2's block has delayed for 11 seconds, and produced 2 blocks in a row. But likely a fork starts just at maintenance interval would cause witness schedule change, then result in longer fork resolution time.
I think it would be better to avoid stake change at maintenance interval, which include trading, transferring, price feeding (which could cause margin calls)..
@Fox: any idea?