Compare
glnc vs Etherscan
Etherscan is excellent at what it is: a deep, label-rich web explorer with verified contract source and a decade of indexed history. If you have ever opened it to read a proxy implementation or to dig through a forgotten airdrop, you know why it has stayed the default.
glnc is excellent at what it is: a terminal-native CLI that does the parts of Etherscan that should never have required a browser tab in the first place. Wallet balances, decoded transactions, live gas, scripted alerts. These are different products. The friction Etherscan creates is the friction glnc removes.
Quick recommendation
Use Etherscan for verified contract source, label-rich exploration, and historical depth. Use glnc for scripting, monitoring, multi-wallet portfolios, and quick checks. The friction Etherscan creates is the friction glnc removes.
Side by side
Where each tool sits on the spectrum from "label-rich browsing" to "programmable inspection."
| Feature | Etherscan | glnc |
|---|---|---|
| Wallet balance, single chain | Yes. Web UI, label annotations, historical charts. | Yes. Terminal output, USD totals, copy-pasteable into scripts. |
| Wallet balance, multi-chain in one command | No. One explorer per chain. | Yes. Auto-detect from the address; per-chain breakdown plus grand total. |
| Verified contract source | Yes. The reason most people are there in the first place. | No. Out of scope; glnc points you at the explorer when source matters. |
| Label database | Yes. Exchange wallets, MEV bots, common contracts, ENS reverse. | No. ENS reverse only. Labels are not part of the product. |
| Read transaction calldata | Yes, with decoded view if the ABI is verified. | Yes, with token movements walked from receipt logs; Universal Router, Governor, MultiSend. |
| Live gas across chains | Per-chain UI on each explorer. | glnc gas covers nine chains in one command; --watch for live updates. |
| Pipe output to jq, cron, Slack | No. Web first. API exists but is shaped for web responses. | Yes. Versioned JSON envelopes on every command. NDJSON under --watch. |
| API key required | Yes for the API. Free tier exists with a low rate limit. | No. Free public RPCs by default. Optional keys lift specific rate limits. |
| Sign in / account | Optional for browsing; required for the API. | No account anywhere. Nothing phoned home. |
| Free | Free tier with paid plans above. | MIT, free forever. |
When Etherscan is right
- Verified contract source. Reading what a proxy implementation actually does is the canonical Etherscan task and glnc does not try to replicate it.
- Label-rich exploration. "Who is this address" is often answerable in one click on the explorer and not at all in a CLI.
- Deep historical sweep. Pagination through years of transactions is genuinely useful in a UI and miserable in a shell.
- Occasional non-engineer use. Sending an Etherscan link to someone who does not have a terminal is the obvious move; do not ship a CLI command.
When glnc is right
- Scripting. Anywhere you would otherwise be screen-scraping or hitting the API with curl. Versioned JSON is the entire point.
- Monitoring.
--watchon balance or gas pipes into cron, into Slack via webhook, into anything that reads NDJSON. - Multi-chain portfolio. One address across nine chains, one command, one grand total. Etherscan needs nine tabs.
- Anywhere you would want to pipe output. If the next step is
jq, the previous step should not be a browser. - No-API-key workflows. First-run, throwaway, CI-job, untrusted-laptop: glnc works without a signup form.
Use both
Use Etherscan in the browser for one-off deep dives. Use glnc in the terminal for everything that repeats. The decision is almost always "am I going to do this again, in some form, in the next week." If yes, write it as a glnc pipeline today. If no, open the tab and move on.