Proxy Contract Viewer

WHAT IT DOES

Proxy Contract Viewer lets you inspect any proxy contract to find its current implementation address, admin address, and beacon address (if used). You provide the proxy contract address, and the tool reads the ERC-1967 standard storage slots directly from the chain. It displays the implementation address (where the proxy delegates calls), the admin address (who can upgrade the proxy), and optionally the beacon address if the proxy uses a beacon pattern. This is essential for developers auditing upgradeable contracts, verifying proxy configurations, and understanding the upgrade path of a contract. It reads the current network chain ID from your wallet provider to ensure queries are directed to the correct network.

HOW TO USE

Connect your wallet using the "Connect" button (required for RPC access). Select the target network (Ethereum Mainnet, Sepolia, Polygon, BSC, Arbitrum, Optimism, and testnets are supported). Enter the proxy contract address. Click "Look up" — the tool will read the ERC-1967 storage slots from the chain and display the implementation, admin, and beacon addresses. Results are shown with links to block explorers for easy verification. The entire operation is read-only — no transactions are signed or sent.

TECHNICAL MECHANISM

The tool reads from three well-known ERC-1967 storage slots: the implementation slot (0x360894a13ba1a3210667c828492db98dca3e2076cc3735a920a3ca505d382bbc), the admin slot (0xb53127684a568b3173ae13b9f8a6016e243e63b6e8ee1178d6a717850b5d6103), and the beacon slot (0xa3f0ad74e5423aebfd80d3ef4346578335a9a72aeaee59ff6cb3582b35133d50). It uses the provider's getStorageAt method to read the raw 32-byte values at these slots, then extracts the last 20 bytes to form the address. The tool does not rely on any contract ABI or function calls — it reads storage directly, making it compatible even if the proxy does not expose view functions. The tool uses ethers.js v5.7.2 and the wallet's provider for all chain interactions. It displays the results in a clear format with links to block explorers. If the implementation slot is zero, the tool indicates that the proxy may not be initialized or may not be an ERC-1967 proxy.

WHAT IT CANNOT SEE

The tool cannot verify if the proxy contract actually implements the ERC-1967 standard — it assumes the slots are used as defined. It cannot detect proxies using non-standard storage slots (e.g., older TransparentUpgradeableProxy patterns, Diamond proxies, or custom implementations). It cannot read implementation addresses if the proxy is not yet initialized or has been upgraded without emitting events. It cannot verify the security or correctness of the implementation contract. It cannot detect if the proxy is a UUPS proxy vs. a transparent proxy — both use the same slots. It cannot read proxy metadata such as upgrade history, timestamps, or who performed upgrades. It is limited by RPC provider availability and rate limits.

PLEASE NOTE

This tool is for educational and analytical purposes. Always cross-reference the implementation address with the block explorer to verify the contract code. The tool does not persist any data; all state is lost on page reload. EVM chains only.