Etherscan — block explorer data for transparent decoding
Etherscan's verified contract ABIs power our smart-contract decoding. We use them to give you readable transaction descriptions instead of opcode dumps.
Etherscan provides the verified-contract database that makes our smart-contract decoding possible. When a transaction touches a verified contract on Ethereum (or any EVM chain with a corresponding scan site), we pull the ABI from Etherscan and decode the function call into something a finance team can read. Address labels and tags are also pulled where applicable.
What the Etherscan integration provides
Verified contract ABIs
Contract function calls decoded with parameter names.
Address labels
Public address tags applied where Etherscan has them.
The connection in 4 steps
Add your Etherscan API key to Wag3s
Register for an Etherscan API key at etherscan.io (free tier works for most use cases). Paste the key into the Wag3s data-integrations panel. Keys for Arbiscan, Optimism Etherscan, Basescan, and Polygonscan can be added separately for multi-chain coverage.
Contract ABIs fetched and decoded automatically
When Wag3s encounters a smart-contract interaction, we query Etherscan for the verified ABI. Function parameters are decoded into human-readable names — "swapExactTokensForTokens" instead of "0x38ed1739".
Address labels enrich the audit trail
Known address tags from Etherscan (exchange deposit wallets, protocol contracts, ENS names) are applied to transaction counterparties in the audit trail.
Secondary source for transaction verification
Etherscan data is used as a secondary verification source alongside RPC node data, ensuring transaction completeness on high-throughput wallets. Discrepancies between sources are flagged for investigation.
Common configurations
Protocol treasury interacts with multiple smart contracts (DEXes, lending protocols, bridge contracts). Raw calldata is unreadable without ABI decoding. The Etherscan integration ensures every transaction in the Wag3s audit trail shows the decoded function name and parameters, making the auditor's review practical.
Compliance officer needs to confirm that outgoing transfers went to known counterparties, not unidentified wallets. Etherscan's public address tags — combined with Arkham labels — provide a first-pass counterparty identification layer across all transactions.
Etherscan integration questions
Is the Etherscan API key required or optional?
Optional — Wag3s functions without it for basic accounting. However, having an Etherscan API key significantly improves transaction decoding quality (readable function names instead of raw calldata) and address labelling. We recommend adding one for all workspaces with significant smart-contract interaction.
Are chains other than Ethereum covered?
Yes. Wag3s supports API keys from Etherscan's family of block explorers — Arbiscan (Arbitrum), Optimistic Etherscan, Basescan, Polygonscan, Snowscan (Avalanche), and others. One key per chain is needed.
What if a contract is unverified on Etherscan?
For unverified contracts, Wag3s falls back to our internal ABI database and known protocol signatures. The function selector is matched against our library of known DeFi protocol calls. Truly unknown function selectors are flagged in the audit trail for manual classification.
Other connectors that pair with this one.
Connect Etherscan in minutes
Free during Alpha. No credit card. Native sync, audit trail, no spreadsheets.