Proxy Delegation Chain Debugger

WHAT IT DOES

Proxy Delegation Chain Debugger helps you understand the complete implementation hierarchy behind a proxy contract. You provide a proxy address, and the tool recursively follows the EIP‑1967 implementation slot (0x360894a13ba1a3210667c828492db98dca3e2076cc3735a920a3ca505d382bbc) to discover the entire chain of delegated implementations. It also detects and reports the admin slot (for upgrade authorization) and the beacon slot (for beacon proxies). The output is a visual chain showing each contract in the delegation path, its type (proxy, implementation, or beacon), and bytecode size — making it easy to understand how a proxy delegates calls across multiple layers.

HOW TO USE

Enter the proxy contract address you want to inspect. Optionally provide a custom RPC URL if you are not connected via wallet. Click "trace delegation chain". The tool fetches the storage slots from the blockchain and recursively follows each implementation reference until it reaches a contract that is not a proxy. Results are displayed as a visual delegation chain with each node showing its address, type, and bytecode size. The admin address is also displayed if present. Use this to audit upgradeable contracts, verify that the expected implementation is active, and understand the full delegation path before performing upgrades or interacting with the proxy.

THE REAL MECHANISM

The tool uses ethers.js v5 to connect to the blockchain via the provided RPC URL or the connected wallet. It reads the implementation slot at the EIP‑1967 standard address. If the slot contains a non‑zero address, the contract is a proxy; the tool then recursively reads the implementation slot of that address, continuing until it finds an address that is not a proxy. It also reads the admin slot (0xb53127684a568b3173ae13b9f8a6016e243e63b6e8ee1178d6a717850b5d6103) to identify the upgrade authority, and the beacon slot (0xa3f0ad74e5423aebfd80d3ef4346578335a9a72aeaee59ff6cb3582b35133d50) for beacon proxies. The recursion depth is limited to prevent infinite loops, and the tool detects cycles automatically. Each node's bytecode size is displayed to help distinguish between proxy stub code and full implementation code.

WHAT IT CANNOT SEE

The tool cannot detect custom proxy patterns beyond EIP‑1967, determine if the delegation chain is secure, verify upgrade authorization, detect if implementations are malicious, handle multi‑hop proxies without standard slots, assess storage compatibility across the chain, or detect if the proxy has been paused or frozen. It only reports the addresses in the delegation chain — it does not analyze the code, verify signatures, or assess the security of the upgrade process. Always combine this with a thorough code review and audit.

PLEASE NOTE — EVM CHAINS ONLY

This tool is designed for Ethereum Virtual Machine (EVM) compatible chains that support standard EIP‑1967 storage slots. It may not work correctly with custom proxy implementations that use non‑standard storage locations. All processing occurs in your browser; no contract data is stored or transmitted.