4 contracts of OKX DEX (OKX Wallet swaps) on Ethereum, Base, Arbitrum One and OP Mainnet, checked against the Clear Signing registry and their recent transactions.
Transactions count every call. Senders count each address once per function, so a relayer bot counts once however many calls it sends.
Registry at ef582c2, committed 4 November 2026On-chain reads 6 November 202667,633 transactions a day across 4 contractsThe data, as JSON
ContractsFIG. 01
4 contracts, busiest first
For each: its address and where it came from, the registry's descriptor for it, the functions it formats, and which of its recent calls a wallet could clear-sign.
calldata-OkxDexRouterV1.0.8-suffix-compat.jsonFor OKX DEX router at 0xC8F6…9265 on Base; it does not list this deployment.The functions it formats make up 100% of what recent senders called here.
Functions
0 of 17 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 6 November 2026 · 62,114 a day
calldata-OkxDexRouterV1.0.8-suffix-compat.jsonFor OKX DEX router at 0x28b1…a183 on Ethereum; it does not list this deployment.The functions it formats make up 100% of what recent senders called here.
Functions
0 of 17 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 6 November 2026 · 4,404 a day
calldata-OkxDexRouterV1.0.8-suffix-compat.jsonFor OKX DEX router at 0x7CF6…049A on Arbitrum One; it does not list this deployment.The functions it formats make up 100% of what recent senders called here.
Functions
0 of 17 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 5 – 6 November 2026 · 879 a day
calldata-OkxDexRouterV1.0.8-suffix-compat.jsonFor OKX DEX router at 0xDd5E…83E7 on OP Mainnet; it does not list this deployment.The functions it formats make up 100% of what recent senders called here.
Functions
0 of 17 writable functions formatted
Recent calls
Formatted: 0% of recent transactions, 0% of recent senders1,000 transactions, 2 – 6 November 2026 · 237 a day
Covered means the registry has a descriptor for the deployment and it formats at least 95% of what recent senders called. Partial means a descriptor formats less, or its reach could not be measured. Uncovered means the registry has no descriptor for it.
Described elsewhere means the registry has a descriptor for another deployment of OKX DEX (OKX Wallet swaps), on another chain or at another address, with functions this contract's recent senders call. It does not list this contract, which stays uncovered, and whether it fits is for its owner to check.
By transactions, every call counts. By senders, each address counts once for each function, so a relayer bot counts once however many calls it sends.
A descriptor is not an audit, and wallets decide which descriptors they trust.