Multicall Builder
Runs offlineEncode several read calls into one Multicall3 payload.
one per line — address, calldata
On failure
Calldata2 calls
0x82ad56cb00000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000e0000000000000000000000000a0b86991c6218b36c1d19d4a2e9eb0ce3606eb4800000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000000418160ddd00000000000000000000000000000000000000000000000000000000000000000000000000000000dac17f958d2ee523a2206206994597c13d831ec700000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000000418160ddd00000000000000000000000000000000000000000000000000000000
Send toMulticall3 — same address on most chains
0xcA11bde05977b3631167028862bE2a173976CA11
A failing call returns success: false and the batch continues, so check each result before trusting it.
About multicall builder
Multicall3 batches many read calls into a single RPC request, which is how block explorers and portfolio trackers fetch hundreds of balances without hundreds of round trips. It is deployed at the same address on most chains. This page builds that payload — the encoded calldata and the address to send it to — and stops there; sending it is a job for your node or your wallet. The allowFailure flag decides whether one bad call takes the whole batch down or simply reports its own failure.