ekx-blockscoutlisted

Reading onchain data with Blockscout across Base, Base Sepolia and Unichain — the MCP server, REST API for transactions and token transfers, contract verification, and why we prefer it over Etherscan for reads. Use when inspecting a transaction, listing token transfers, checking whether a contract is verified, or building a link to an explorer in the UI.
Ekinoxis-evm/claude-skills · ★ 0 · AI & Automation · score 60

Install: claude install-skill Ekinoxis-evm/claude-skills

# Blockscout **Our default block explorer for reads.** Configured as an MCP server in the onchain repos. --- ## Instances | Network | URL | |---|---| | Base mainnet | `https://base.blockscout.com` | | Base Sepolia | `https://base-sepolia.blockscout.com` | | Ethereum Sepolia | `https://eth-sepolia.blockscout.com` | | Unichain | `https://unichain.blockscout.com` | | Unichain Sepolia | `https://unichain-sepolia.blockscout.com` | ```bash BLOCKSCOUT_PRO_API_KEY= # optional — higher rate limits ``` --- ## Why Blockscout over Etherscan 1. **It has an MCP server**, so Claude can read chain state directly during development. 2. **Open API, generous unauthenticated limits** — Etherscan's free tier throttles hard. 3. **Verified source is readable via API**, useful for auditing a dependency mid-task. We still verify contracts on **both** Blockscout and Basescan — Basescan is what most users click through to, Blockscout is what our tooling reads. --- ## REST basics ```bash # Token transfers for an address curl "https://base-sepolia.blockscout.com/api/v2/addresses/$ADDR/token-transfers" # A transaction curl "https://base-sepolia.blockscout.com/api/v2/transactions/$TXHASH" # Is this contract verified? curl "https://base-sepolia.blockscout.com/api/v2/smart-contracts/$ADDR" ``` The `/api/v2/` namespace is the current one. `/api?module=…` is the Etherscan-compatible legacy shim — it works, but returns less. --- ## Verifying from Foundry ```bash forge verify-contract <ADDR>