The chainstate/ listing incorporates a LevelDB database. There isn’t a assure by any means that two LevelDB databases with the identical content material are an identical (and even have the identical measurement).

LevelDB internally constructions their database storage as quite a lot of desk recordsdata, every containing keys of some vary of keys with the corresponding values. A number of recordsdata can cowl overlapping ranges of keys. There are heuristics internally within the database logic to find out when these desk recordsdata get merged and compacted into new ones, however there are laborious to foretell, as they depend upon the precise order issues have been written in.

And it is very a lot anticipated that was what written to those two databases you observe differs, even when their contents is an identical. One node has been working for years, so it’s going to have typically a write with updates as soon as per block or per few blocks at most. The node that only in the near past accomplished preliminary block obtain (IBD) could have seen far fewer (however greater) writes matching many blocks without delay, as Bitcoin Core flushes a lot much less incessantly throughout IBD for efficiency causes. Moreover, on account of inner in-memory caching in Bitcoin Core, many UTXOs could have been created and spent between two updates within the IBD case, inflicting them to by no means hit disk in any respect.