Simple Base SwapSimple Base SwapOpen app
← All articles
Nov 11, 2026·5 min read

Multicall Contracts Explained: Why One Transaction Can Do Several Things

basebasescansmart contractswallet safety
base

If you have ever looked up a transaction on a block explorer and seen it labeled as an interaction with a contract simply called Multicall, rather than the name of the app you thought you were using, you have run into one of the more common but least explained patterns in onchain software. It is not a scam and it is not unusual. It is a basic tool that lets a single call do the work of several, and it shows up everywhere from wallet balance checks to swaps.

The basic idea: bundling calls together

Normally, each read or write to a smart contract is its own separate call. If you wanted to check the balance of five different tokens in a wallet, a naive approach would make five separate requests to the blockchain, one after another. If you wanted to approve a token and then swap it, that is traditionally two separate transactions, each needing its own confirmation and its own gas payment.

A multicall contract exists to bundle several of these calls into one. Instead of five separate requests, an app sends one request to the multicall contract, which forwards each of the five calls on its behalf and returns all five answers together. Instead of two transactions for an approval and a swap, some apps build a single transaction that performs both steps through a router that does its own internal batching.

The pattern comes in two flavors that are useful to tell apart, because they have different consequences for you as a user.

Batching reads costs you nothing

The first flavor is batching reads. This is what happens when an app wants to know several things from the chain at once, such as your balances across a handful of tokens, or several accounts' allowances. Reads do not change anything onchain and do not need your signature, so this kind of multicall happens silently in the background. It is purely an efficiency trick for the app, cutting down the number of network round trips so a page loads faster. You will never be asked to approve this kind of multicall, because nothing is being written anywhere.

Batching writes is what shows up in your wallet

The second flavor is batching writes, meaning the call actually changes state, moves tokens, or updates a balance. This is the one that reaches your wallet as a transaction you need to sign, and it is also the one you should actually read before approving.

A common example on Base is a swap router that combines an approval and a swap, or a swap and the transfer of the output tokens, into a single multicall transaction so you only pay gas and sign once instead of twice. Liquidity positions, batched claims across several reward contracts, and some NFT minting flows use the same approach. The appeal for you as a user is fewer signatures and lower total gas, since you are paying for one transaction's overhead instead of several.

The tradeoff is that a single signature is now authorizing a sequence of actions instead of one obvious action, so it is worth slowing down slightly before approving. Your wallet's confirmation screen is still the most reliable place to see what will actually happen, more reliable than the app's own interface, because it reflects what the transaction will do rather than what the app claims it will do. If your wallet shows a plain-language simulation listing each step a multicall transaction will perform, read through all of them, not just the first one.

Multicall3: the specific contract you will often see

A large share of the "Multicall" labels you will encounter on Base, and on most other EVM chains, point to the same contract: Multicall3, deployed at the address 0xcA11bde05977b3631167028862bE2a173976CA11. This is not an app-specific contract that any one project built. It is a shared, open source utility maintained by the developer mds1 and deployed at the identical address on dozens of EVM chains, including being included as a preinstalled contract in Base's own chain configuration. Wallets, block explorers, and dapp frontends commonly use this same deployment to batch their read calls, which is why you may see the identical contract address show up regardless of which app you were actually using.

Because it is so widely shared and purely mechanical, seeing Multicall3 in your transaction history is not itself a signal of anything good or bad. It tells you an app chose an efficient way to fetch data or bundle actions. It does not tell you whether the actions it bundled were the ones you wanted.

What is actually worth checking

The useful habit is the same one that applies to any wallet confirmation, just applied with a bit more attention because a multicall transaction does more in one step:

  • Look at how many distinct actions the confirmation screen lists, not just the total value moving.
  • Check that any token approval included in the bundle is for the amount you intend, not an unlimited allowance you did not ask for. Our guide on checking and revoking token approvals covers how to review these after the fact.
  • If a transaction bundles far more steps than the action you clicked should need, treat that as a reason to pause rather than a reason to assume efficiency.

The takeaway

Multicall is a plumbing detail, not a protocol you need to seek out or avoid. It exists so apps can ask the chain several questions at once for free, and so they can occasionally bundle several signed actions into a single transaction to save you gas and clicks. Seeing it labeled on a block explorer just means the app chose a common, well understood shortcut. What still matters, exactly as it does without multicall, is reading what your wallet says the transaction will actually do before you approve it.

Ready to try it yourself?

Create a non-custodial wallet on Base in seconds. No account, no sign-up.

Open the web app