What would make a blockchain lag 50-100 blocks behind? [closed]

Related: How to run bitcoind in a low memory environment

I am following the advice in the accepted answer to the question above. I am running a collection of coins next to each other on a server. I find that this seems to work well for PoW based coins but it seems to be quite disastrous for PoS coins.

ZEN (Horizen PoW)
DOGE (Dogecoin PoW)
ASAFE (Allsafe PoS)
NBX (Netbox PoS)

What I see with ZEN when I getbestblockhash then put the hash into the block explorer is 1 confirmation, as is the case with DOGE. But with the same settings ASAFE is lagging by 114 blocks and NBX by 34 from the real blockchain tip. (all after syncing)

In each conf I have these settings:

dbcache=40
maxsigcachesize=4
maxconnections=4
rpcthreads=3
blocksonly=1
listenonion=0
par=3
prune=2048
txindex=0
maxorphantxsize=10

The thing that I find odd is the consistency of the lagging in both ASAFE and NBX (that they stay at 114 and 34 without much alteration 113, 32 sometimes for example). If I watch tail the debug.log then I see new blocks are being processed as seen yet, they seem to not be making effort to advance (as if it has decided to stop, stay behind and only wait for blocks). What I am trying to say is; from my own experience, I program in JavaScript/Node.js scripts that deal with blockchain and I see my scripts process 100 transactions in a couple of seconds, lots of lines of code executed each second and C++ is suppose to be faster. I am wondering if one of the changes to the confs is the cause?

You can get bonuses upto $100 FREE BONUS when you:
💰 Install these recommended apps:
💲 SocialGood - 100% Crypto Back on Everyday Shopping
💲 xPortal - The DeFi For The Next Billion
💲 CryptoTab Browser - Lightweight, fast, and ready to mine!
💰 Register on these recommended exchanges:
🟡 Binance🟡 Bitfinex🟡 Bitmart🟡 Bittrex🟡 Bitget
🟡 CoinEx🟡 Crypto.com🟡 Gate.io🟡 Huobi🟡 Kucoin.