API Console — REST endpoints for ENK data and Ethereum search.
API Reference

EnteleSCAN API

Read-only Ethereum JSON-RPC observability endpoints for ENK and Ethereum data.

All endpoints accept GET requests. Base URL: https://www.entelescan.com/api/

ENK Token Supply

GET /api/enk?action=supply

Returns total on-chain ENK supply for contract 0xC95343B3f8A5af57a9b3B1acFf3D2a7654Fa28F6 on Ethereum mainnet using an eth_call against totalSupply().

Response: compatibility JSON with status, message, result (raw 18-decimal supply), and source.

ENK Recent Transfers

GET /api/enk?action=transfers

Returns up to 10 recent ENK Transfer logs from bounded Ethereum block windows. If no recent log is available in the bounded lookup window, the result may be an empty array rather than fabricated activity.

Network Statistics

GET /api/search?action=stats

Returns live Ethereum chain information, ENK supply, latest block, gas price, search modes, and source status. The endpoint reports live only when the authoritative RPC snapshot is complete; otherwise it fails closed with a limited/unavailable response.

Fields: status, chain, chainId, latestBlock, safeGasGwei, enkSupply, searchModes, source

Universal Search

GET /api/search?q={address_or_hash}

Recognizes and resolves Ethereum wallet addresses, contract addresses, and transaction hashes directly against Ethereum JSON-RPC.

Transaction hash: 66-character 0x hex string — returns block, from/to, value, gas and success state when available.

ENK contract: Recognized from the ecosystem registry and verified against live Ethereum bytecode state.

Other addresses: Returns wallet/contract type and live ETH balance. EnteleSCAN does not invent transaction history when an RPC provider does not expose indexed account history.

ENK Contract Reference

ParameterValue
Contract0xC95343B3f8A5af57a9b3B1acFf3D2a7654Fa28F6
Chain ID1 (Ethereum)
Decimals18
Max Supply100,000,000,000 ENK

Runtime source

Core production data uses server-side Ethereum JSON-RPC and does not require an Etherscan API credential. Operators may set ETHEREUM_RPC_URL to a dedicated Ethereum mainnet provider. If authoritative chain data cannot be resolved, the API returns a fail-closed unavailable/limited response instead of labelling stale or failed upstream data as live.

Explorer links and rate limits

Etherscan is used as the external user-facing explorer for contract and transaction links, not as a required EnteleSCAN runtime data credential. JSON-RPC request limits depend on the configured Ethereum provider. For production integrations, contact team@entelescan.com.