How to Read a Multisig Wallet Transaction on an Explorer

27 October 2026

A multisig wallet transaction on a block explorer looks different from a regular transaction because it involves multiple signers, a threshold, and often a separate execution step. To read it, you need to identify the multisig contract address, locate the transaction that submitted the signatures, and check whether the threshold was met before the action executed.

First: confirm the wallet is multisig

Before digging into any transaction, verify that the sending or receiving address is a multisig wallet, not a regular externally owned account (EOA). On an explorer, look at the address page. If it shows a contract creator and a contract name like "Gnosis Safe" or "MultiSigWallet," you are looking at a contract. If you see transaction history that includes "execution" or "confirmation" calls, that is another clue. A standard EOA will have no contract tab and no internal function calls.

The two transaction types in multisig

Multisig wallets typically use two kinds of on-chain transactions:

• Confirmation transactions - Each signer submits a transaction that records their approval. These are often internal transactions or separate contract calls.
• Execution transaction - Once enough confirmations are collected, someone (anyone, not necessarily a signer) submits a transaction that actually performs the intended action, like sending tokens or calling another contract.

On most explorers, the execution transaction is the one you see on the main transaction list. The confirmations may be hidden inside that transaction as internal transactions or listed separately on the wallet’s page.

Step-by-Step: reading a multisig execution transaction

1. Open the Transaction on the Explorer

Click into the transaction hash. You will see the standard fields: from, to, value, gas used, and input data. The "to" field will be the multisig wallet contract address, not the final recipient. The value shown is usually 0, because the actual transfer happens inside the contract.

2. Check the Input Data

Click the "Input Data" or "Decode Input Data" tab. This shows the function called on the multisig contract. Common function names:

• submitTransaction - A signer submits a proposed action. This is not the final execution; it just records the intent.
• confirmTransaction - A signer adds their approval to an existing pending transaction.
• executeTransaction - The final call that runs the action after enough confirmations.

If you see executeTransaction, the decoded data will contain the actual destination address, value, and data payload of the intended action. That is where you find what the multisig actually did.

3. Look at Internal Transactions

Most explorers have an "Internal Transactions" tab or a "More" dropdown. Open it. Here you will see the calls made by the multisig contract during execution. The key internal transaction will show:

• From: The multisig contract address
• To: The actual recipient (could be a wallet or another contract)
• Value: The amount of native coin (ETH, BNB, etc.) sent
• Input Data: If the multisig called another contract, the data appears here

If the multisig sent an ERC-20 token, you will see an internal call to the token contract with a transfer function. The value in that internal call is the token amount, not the native coin.

4. Verify the Threshold

Scroll to the "Logs" or "Events" section of the execution transaction. Multisig contracts emit events like Confirmation or ExecutionSuccess. Look for an event that states the number of confirmations and the required threshold. For example, a Gnosis Safe emits an ExecutionSuccess event with a threshold parameter. If you see that the threshold was 2 of 3, and the execution happened, then enough signers approved.

If you cannot find the threshold in the logs, go to the multisig wallet’s contract page on the explorer. Look for a read function called required or getThreshold. Call it with no parameters (or the transaction nonce) to see the current required number of signers.

What about the signers?

To see who signed, you need to look at the confirmation transactions. On the multisig wallet’s address page, filter transactions by "Internal Txns" or look for "Transaction" events. Each confirmation transaction will show the signer’s address in the "from" field and a call to confirmTransaction with a specific transaction ID (nonce). Count the unique signers. If the count meets or exceeds the threshold, the multisig will execute.

Some explorers (like Etherscan for Gnosis Safe) have a dedicated "Multisig" tab on the wallet page that lists pending and executed transactions along with signer confirmations. Use that when available; it is faster than manual searching.

Common confusion: why the value is zero

If the multisig sent 10 ETH, the main transaction line will show "Value: 0 ETH." That is normal. The 10 ETH moved inside the internal transaction. The main transaction only paid gas for the contract call. Always check internal transactions or decoded input data for the real value.

What if you see a failed multisig transaction?

A multisig transaction can fail at execution if:

• The threshold was not met (the executeTransaction call was made too early)
• The intended action itself reverted (e.g., the target contract rejected the call)
• Gas ran out during the internal calls

Check the transaction status. If it says "Failed," look at the revert reason in the input data or error logs. The multisig contract did not fail because of a bad signature; it failed because the underlying action could not complete. The signatures themselves are still valid.

Summary

To read a multisig wallet transaction on an explorer, focus on the execution transaction first. Decode its input data to see the intended action, then inspect internal transactions for the actual transfer. Count confirmations from the wallet’s event logs or dedicated multisig tab. The value you care about is almost never on the main transaction line - it is one layer deeper.

Back to block explorers