Sorry to give my two pieces about Kaspa forks, because I see a lie here.

The explorer's rest server can give out wrong information only in two cases.
1. The network consensus has been modified and it is broken.
2. The explorer's database has been altered.

In those two cases the explorer could display wrong information and both of the cases would require modifications to the code and data.

Because this is how things work in Kaspa world:
1. Blockchain consensus does it's magic when blocks are mined.
2. Database filler reads the blockchain and moves data to explorers database. 
3. Explorer rest server and socket server serve the data for explorer front-end.
4. Explorer database filler, rest server nor socket server  do not validate any data, they just take data as is from the blockchain.

It is really odd that someone blames code that is working for ~20 Kaspa forks.