Incorrect order of Transaction History during programmatic tx executions

[AdvayAgrawal]

Bug description

On executing safe transactions directly using contract functions rather than the UI, probably because a bunch of transactions were executed at the same time, the transaction history shows me the data which isnt ordered correctly by nonce.

Environment

• Browser: Brave
• Wallet: MetaMask
• Chain: BSC mainnet

Steps to reproduce

1. Use a script to execute multiple transactions together

function executeAirdrops() external {
        string memory json = vm.readFile("script/outputs/txHashes.json");
        string[] memory files = json.readStringArray(".files");
        ISafe safe = ISafe(receiver_multisig);

        vm.startBroadcast();

        for (uint256 i = 0; i < files.length; i++) {
            .
            .
            .
            safe.execTransaction(
                multiSendContract,
                0,
                multiSigCalldata,
                Enum.Operation.DelegateCall,
                0,
                0,
                0,
                address(0),
                payable(address(0)),
                mergedSignature
            );
        }

        vm.stopBroadcast();
    }

2. Run the script using foundry (forge script)
3. After successful execution through script, Visit the history tab on safe UI, to see the transactions.

Expected result

All transactions visible, ordered by nonce

Obtained result

All transactions are visible, but not ordered.

Screenshots

[liliya-soroka]

@AdvayAgrawal , could you provide the safe address to check ?

[AdvayAgrawal]

@liliya-soroka Sure, here you go
https://app.safe.global/transactions/history?safe=bnb:0x2366c3830a9e1FBB5Ea0B6BC4Bb9717A8f2B8490

[liliya-soroka]

thank you, the team is checking

[AdvayAgrawal]

Alright great. Thanks

[AdvayAgrawal]

Hi @liliya-soroka
Any updates on this issue?

[PooyaRaki]

Hi @AdvayAgrawal,

Thanks for reporting the issue. We’ve investigated it and confirmed that it’s a purely visual glitch—functionality remains unaffected and behaves as expected.

The issue arises because transactions are displayed based on their execution time. When multiple transactions are executed simultaneously, the UI may show them in a slightly confusing order. Since transactions cannot be executed out of nonce order (i.e., a lower nonce cannot be executed before a higher one), executing them at different times results in a clearer ordering.

That said, we recognize the confusion this can cause and will prioritize a fix to improve the visual clarity.

Cheers,

[AdvayAgrawal]

Hey @PooyaRaki,
Thanks for your response! I agree — it's just a visual glitch in the UI and doesn't affect any functionality. I mainly raised it so the order can be displayed based on the nonce value rather than execution timestamps, which might help avoid confusion.
Just to mention, the same happened today too after executing a bunch of other transactions.

Appreciate you taking the time to look into it, thanks!