We built and integrated a batch-send widget into a major multichain block explorer
Result: A fully embedded batch-send feature shipped to millions of users across 30+ chains, turning a read-only explorer into a transactional platform.
Client name withheld under NDA.
// problem
A leading multichain blockchain explorer serving 30+ networks needed to expand its feature set beyond passive data browsing. The platform had millions of monthly users looking up transactions, tracking portfolios, and monitoring cross-chain bridge activity. But every time a user wanted to take action on what they found—such as distributing tokens to multiple wallets, executing batch payments, or processing airdrop distributions—they had to leave the site and go to a separate tool.
That workflow leak was a problem on two fronts. Users lost context and convenience. The explorer lost engagement and the opportunity to become a transactional platform, not just a read-only one. They wanted an embedded widget that let users send tokens to multiple addresses in a single transaction, directly from the explorer interface, without ever navigating away.
// how we solved it
Our engineering pod built a multisender widget and integrated it into the explorer’s cross-chain interface via API. The widget supports batch token transfers across EVM-compatible chains, allowing users to upload recipient lists, preview gas estimates, approve token spend, and execute multi-send transactions, all within the explorer’s existing UI.
The integration required careful coordination with the explorer’s existing wallet connection layer, chain-switching logic, and transaction rendering pipeline. We built the widget as a modular, embeddable component that respected the explorer’s design system and performance requirements. The entire build, from scoping through deployment, was handled end to end by our pod: two full-stack engineers on the widget and API layer, one DevOps engineer on deployment and monitoring, one QA engineer on cross-chain transaction validation, and a project manager coordinating with the explorer’s internal team.
The result was mutually beneficial. The explorer gained an integrated transactional feature that increased user engagement and time-on-site. The multisender product gained distribution to a massive existing user base without needing to acquire that traffic independently.
// outcome
A fully embedded batch-send feature shipped to millions of users across 30+ chains, turning a read-only explorer into a transactional platform.
Want a system like this for your team?
Book a Discovery Call