MongoDB stale replication, odd timestamp after data flush
No, it's not expected be there. Timestamp values should be decimal, not hexadecimal and msec value 3b1 is bigger than 333.

You could "move" primary status from current node to another node and try to resync this stale node again, this time it would read that other node and hopefully it's opLog is in good condition.