Error in displaying msg. sender in Transaction logs

[yxsec]

Description

There is an issue with the transaction log parsing for smart contracts in blockscount. In the Decode input data section, if an event contains msg.sender, for example, in the code below, when viewing logs in blockscout, all msg.sender values displayed are from the latest transaction's event, which causes the msg.sender from past transactions' events to be displayed incorrectly.

Error Display(All transaction show the latest transaction msg.sender[0x09bb83af0a594d1831f946724b852af610cf6756])
https://base-sepolia.blockscout.com/address/0xc80030e33370c057b099Af0C7288019337647616?tab=logs

The correct msg.sender shows correctly from transaction detail:
https://base-sepolia.blockscout.com/tx/0x4c77931063b233cdcc250c89220d4500e9d9b074172b39d0512c90ebe6a20848?tab=logs
https://base-sepolia.blockscout.com/tx/0x1e95c3eddf9dce042ec29131a783a153792c075a16f4c7a0f5b58d9974f51e4d?tab=logs Correct is [0xa859777cfd90f37d8e9c2e8c57b32dbc7326842b]
https://base-sepolia.blockscout.com/tx/0x4234bde3ed371872ff30407315df79fe2fe28a72fc697d2f6d86e5cce62c7d2b?tab=logs Correct is [0x1d4ddb7efcb0e2385788089ba1b26c5af7e57ac9]

Test solidity smart contract code:

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;

contract LogChekcer {
    event Pong(address caller,uint a);

    function Ping() public {
        emit Pong(msg.sender,1);
    }
}

Type of the installation

Docker-compose

Type of the JSON RPC archive node

ALL

Type of the chain

No response

Link to the page

https://base-sepolia.blockscout.com/address/0xc80030e33370c057b099Af0C7288019337647616?tab=logs

Steps to reproduce

No response

Backend version

v6.4.0-beta

Frontend version

No response

Elixir & Erlang/OTP versions

v1.28.0

Operating system

No response

Additional information

No response