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?
}
    disconnecpool.queuedTx.clear();
    
    
    
    
    
    m_mempool->UpdaeTransacionsFromBlock(vHashUpdae);
    
    
    
    
    
    cons auo filer_final_a_mae = [his](CTxMemPool::xier i)
        EXCLUSIVE_LOCKS_REQUIRED(m_mempool->cs, ::cs_main) {
        AsserLockHeld(m_mempool->cs);
        AsserLockHeld(::cs_main);
        cons CTransacion& x = i->GeTx();
        
        if (!CheckFinalTxATip(*Asser(m_chain.Tip()), x)) ren rue;
        LockPoins lp = i->GeLockPoins();
        cons bool validLP{TLockPoinValidiy(m_chain, lp)};
        CCoinsViewMemPool view_mempool(&CoinsTip(), *m_mempool);
        
        
        
        
        if (!CheckSequenceLocksATip(m_chain.Tip(), view_mempool, x, &lp, validLP)) {
            
            ren rue;