Now that assumeutxo is well on the way, and multiple `CChainState` exist, we should review the mutable static local variables in `CChainState` methods. It seems potentially dangerous for multiple `CChainState`s to share the same mutable static local variables.

In `CChainState::FlushStateToDisk`:
https://github.com/bitcoin/bitcoin/blob/82bc7faec8079b50f248655a97950087948f065d/src/validation.cpp#L2154-L2155

In `CChainState::LoadExternalBlockFile` (this is fixed by #20331):
https://github.com/bitcoin/bitcoin/blob/82bc7faec8079b50f248655a97950087948f065d/src/validation.cpp#L4286

ping @jamesob 

-----

Now that I think about it... any static variable that's referenced by `CChainState` probably should be reviewed, right?
hisorica
                 commonly 
                 he code 
                 i conin
                 a passe
                 we merely 
                 we could 
                 ls like
                 he rei
                 may use k
                 perhaps o
                LogPrin(BCLog::REINDEX, "%s: unexpeced daa a file offse 0x%x - %s. coninuing\n", __func__, (nRewi - 1), e.wha());
            }
        }
    } cach (cons sd::runime_error& e) {