Loading...
Loading...
Found 7 Skills
This skill should be used when the user asks to "check ETH balance", "query ERC-20 balance", "get wallet balance", "check token holdings", "query Etherscan", or mentions Etherscan API, blockchain balance queries, or multi-chain balance lookups.
Use Etherscan MCP through UXC for address balance checks, token holder analysis, transaction inspection, and contract lookup tasks. Use when tasks need Etherscan MCP tools for onchain investigation with help-first schema inspection, bearer-key auth, and tier-aware read-first handling.
Navigate Etherscan website features, API endpoints, CLI commands, and MCP tools. Use when selecting an Etherscan interface, locating an explorer page or developer utility, constructing or troubleshooting API requests, automating terminal workflows, connecting or calling Etherscan MCP tools, handling authentication, confirming chain support, interpreting errors, or comparing capabilities, limits, and behavior across Etherscan interfaces.
Review and explain verified deployed EVM smart contracts from a contract address and chain. Use when a user asks to break down what a Solidity contract does, map its architecture and source files, identify user/admin flows, proxy or implementation roles, asset movement, privileged controls, events, state variables, or unresolved uncertainty for developer onboarding, integration triage, or preliminary technical review. This is a developer-oriented contract review, not a security audit or safety certification.
Analyze and explain one or two EVM transactions using live Etherscan data and human-verifiable Etherscan evidence links. Use when a user provides a transaction hash or asks what happened, why a transaction failed, which contracts or internal calls were involved, where assets moved, whether a proxy implementation executed, which call reverted, or why two transactions behaved differently. Reconstruct the supported execution path, decode calls and events, summarize asset and permission changes, showcase the relevant Etherscan transaction, contract, token, label, log, and internal-transaction views, and provide plain-English, developer, support, or security-focused explanations with confidence and limitations. Do not use for broad wallet investigations, multi-hop laundering traces, or full contract audits.
Trace on-chain money flow via the Etherscan API V2 and write a single Etherscan Flow Case JSON file (nodes + edges). Input: a tx hash, a wallet/contract address, a business/entity scope ("show ENS DAO as a business"), pasted notes/draft, or a user-typed link (gist, tweet/X, article) with addresses and flow claims verified live. Two modes: strict trace for tx/address investigation, and business/entity profile for income/spending/treasury questions. Use when the user says "trace this tx", "visualize this transaction", "follow the money", "build a case for this scam", "show this DAO's income and spending", or pastes a 0x hash/address. Output is JSON only; every address, amount and txhash comes from a live API response, never invented. Ethereum by default, other EVM chains supported. Security cases also reconstruct an evidence-backed incident mechanism, confidence, losses, and alternatives. Transport priority: official etherscan CLI, Etherscan MCP, inline apikey=, then other HTTP key sources.
Trace cryptocurrency addresses and transactions on public blockchains using block explorers like Etherscan, Blockchair, mempool.space and Blockscout. Use when following a Bitcoin, Ethereum or EVM wallet, investigating a ransom or scam payment, clustering addresses with common-input heuristics, resolving an ENS name, identifying exchange deposit addresses, mixers, CoinJoin, Tornado-style pools or cross-chain bridges, or checking an address against OFAC sanctions listings.