Tradar
Contract search over indexed Ethereum bytecode. Ask which deployed contracts contain a DELEGATECALL, hold an unverified source, or answer a particular function selector — then open any of them in the workbench. Tradar is available today from your account, and every answer states the slice of the chain it was drawn from.
q opcodes: delegatecall and admin_kind: eoa
and verified = false
hit 0x3f8a…d201 1,284 deployments share this code
hit 0x91c4…77be 311 deployments
hit 0xb0e2…4a19 96 deployments
// coverage: incomplete — an indexed slice, not the chain
A search engine over deployed bytecode
Block explorers index transactions and let you look up one address at a time. Tradar indexes what the code does — the opcodes it contains, the selectors it answers, the proxy and admin shape it has — so a question about a whole population of contracts is one query rather than a scraping project.
- IndexedEthereum contract bytecode and the facts recovered from it
- Grouped bycode family — identical code counted once
- Returnsmatching families, the evidence that matched, and the coverage
- Statusavailable today from your account
What you can ask about
One expression language, combined with and / or. Every field below is a fact recovered from the deployed code or its verified source — nothing is inferred from a label someone typed.
Identity
Address, code hash, and code id — the key that treats two deployments of the same contract, differing only in their compiler metadata footer, as one thing.
Interface
Function selectors and how many a contract answers, plus resolved signature names where a 4-byte or Sourcify entry exists for them.
Opcodes
Presence and count of the eight opcodes that decide how a contract can behave: CALL, CALLCODE, CREATE, CREATE2, DELEGATECALL, SELFDESTRUCT, SSTORE, STATICCALL.
Proxy and authority
Proxy shape and type, the implementation behind it, the admin and what kind of account holds it, the declared owner, and the creator.
Source and build
Whether a verified source exists at all, and when it does: compiler, compiler version, language, optimizer runs and EVM version.
Behaviour and links
Whether the code reads or writes storage, which guard patterns are present, the token standard it implements, and which contracts it calls or is called by.
How much of the chain is indexed
Tradar indexes 200,000 deployments — a slice taken from a corpus of 5,982,001 Ethereum contracts — which resolve to 51,338 distinct code families. That slice is the honest number, and the API reports its coverage as incomplete on every response rather than only when a search comes back empty.
It matters because of what a silent index would imply: a query that returns nothing would otherwise read as “no contract on Ethereum does this”, when the truthful answer is “nothing in the indexed slice does this”. Those are different claims and only one of them is supportable.
- NetworkEthereum. No other network is indexed
- Indexed200,000 deployments of 5,982,001
- Code families51,338
- Coveragereported as incomplete on every response
refused — sload is not an indexed opcode
// searchable: call, callcode, create, create2,
// delegatecall, selfdestruct, sstore, staticcall
// the alternative was worse: answering "0 results"
// would read as "no contract writes storage this way"
What a match is, and what it is not
Tradar finds code with a given shape. Deciding whether that shape is a problem in a given contract is the workbench’s job, and it is done by execution — which is why the two are joined rather than merged.
A match is structural
“This contract contains a DELEGATECALL and its admin is a single keypair account” is a fact about the code. It is not a vulnerability, and Tradar does not present it as one.
Proof happens in the fork
Take a candidate into the Auditing IDE, open it on a fork of live chain state, and drive it. A finding is something that replayed — the same bar every other surface is held to.
No monitoring, no alerts
Tradar answers questions you ask. It does not watch the chain, raise alerts, or score contracts for risk on its own. Those are not available.
Find the population, then prove the one
Contract search is in the workbench, beside the surfaces that take a candidate apart.