How do I install the Ekx Blockscout skill?

Run npx skillmds@latest add ekinoxis-evm/ekx-blockscout in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ekx Blockscout safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ekx Blockscout?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ekx Blockscout free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ekx Blockscout?

Ekinoxis-evm (@ekinoxis-evm) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ekx Blockscout by ekinoxis-evm — Agent Skill

Name: Ekx Blockscout
Rating: 4.2 (5 reviews)
Author: Ekinoxis-evm

Ekx Blockscout

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 Updated Sep 22, 2026

File contents

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`

BLOCKSCOUT_PRO_API_KEY=    # optional — higher rate limits

Why Blockscout over Etherscan

It has an MCP server, so Claude can read chain state directly during development.
Open API, generous unauthenticated limits — Etherscan's free tier throttles hard.
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

# 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

forge verify-contract <ADDR> src/Auction.sol:Auction \
  --verifier blockscout \
  --verifier-url https://base-sepolia.blockscout.com/api

No API key needed for Blockscout verification. See ../ekx-foundry/SKILL.md.

Explorer links in the UI

const EXPLORER: Record<number, string> = {
  8453:  "https://base.blockscout.com",
  84532: "https://base-sepolia.blockscout.com",
};
export const txUrl = (hash: string) => `${EXPLORER[CHAIN.id]}/tx/${hash}`;

Always link the transaction after a write completes. Users expect to verify their own transaction — it is the cheapest trust signal available.

Gotchas

Indexing lag. A transaction is queryable on-chain before Blockscout has indexed it. Poll the RPC for the receipt (../ekx-viem-wagmi/SKILL.md), not the explorer.
Instance per network. There is no single multi-chain endpoint.
Unverified contracts return no ABI — verify as part of deploying, not later.
Rate limits without a Pro key are fine for development, thin for a production polling loop. Cache.

---name: ekx-blockscoutdescription: 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.---# 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` |```bashBLOCKSCOUT_PRO_API_KEY= # optional — higher rate limits```---## Why Blockscout over Etherscan1. **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 mostusers click through to, Blockscout is what our tooling reads.---## REST basics```bash# Token transfers for an addresscurl "https://base-sepolia.blockscout.com/api/v2/addresses/$ADDR/token-transfers"# A transactioncurl "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-compatiblelegacy shim — it works, but returns less.---## Verifying from Foundry```bashforge verify-contract <ADDR> src/Auction.sol:Auction \ --verifier blockscout \ --verifier-url https://base-sepolia.blockscout.com/api```No API key needed for Blockscout verification. See [`../ekx-foundry/SKILL.md`](../ekx-foundry/SKILL.md).---## Explorer links in the UI```tsconst EXPLORER: Record<number, string> = { 8453: "https://base.blockscout.com", 84532: "https://base-sepolia.blockscout.com",};export const txUrl = (hash: string) => `${EXPLORER[CHAIN.id]}/tx/${hash}`;```Always link the transaction after a write completes. Users expect to verify their owntransaction — it is the cheapest trust signal available.---## Gotchas1. **Indexing lag.** A transaction is queryable on-chain before Blockscout has indexed it. Poll the RPC for the receipt ([`../ekx-viem-wagmi/SKILL.md`](../ekx-viem-wagmi/SKILL.md)), not the explorer.2. **Instance per network.** There is no single multi-chain endpoint.3. **Unverified contracts** return no ABI — verify as part of deploying, not later.4. **Rate limits without a Pro key** are fine for development, thin for a production polling loop. Cache.

Frequently asked questions