Contract control history
TimelockController on Polygon PoS — who can change it, and what changed
This timelock at 0x32dd…0924 on Polygon PoS sits behind a 2d timelock. Gliese has recorded 8 control changes. Last checked 2026-09-07 00:48:07 UTC.
Timelock2d timelockPolygon PoS
Current control surface
snapshot 2026-09-07 00:48:07 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Timelock delay
- 2dminimum wait between queue and execution
Recorded events
Open in the feed →| Event | Real | Setup |
|---|---|---|
| Call scheduledtimelock.call_scheduled | 8 | 0 |
| Total | 8 | 0 |
Recent changes
Setup-time events hidden- Call to 0x32dd…0924 scheduled, executable after 2dtimelock.call_scheduled · tx 0x0911db0e…4427df · block 93,357,965· 2026-09-07 00:46:21 UTC
- Call to 0x32dd…0924 scheduled, executable after 2dtimelock.call_scheduled · tx 0x0911db0e…4427df · block 93,357,965· 2026-09-07 00:46:21 UTC
- Call to 0x32dd…0924 scheduled, executable after 2dtimelock.call_scheduled · tx 0x0911db0e…4427df · block 93,357,965· 2026-09-07 00:46:21 UTC
- Call to 0x32dd…0924 scheduled, executable after 2dtimelock.call_scheduled · tx 0x0911db0e…4427df · block 93,357,965· 2026-09-07 00:46:21 UTC
- Call to 0x32dd…0924 scheduled, executable after 2dtimelock.call_scheduled · tx 0x0911db0e…4427df · block 93,357,965· 2026-09-07 00:46:21 UTC
- Call to 0x32dd…0924 scheduled, executable after 2dtimelock.call_scheduled · tx 0x0911db0e…4427df · block 93,357,965· 2026-09-07 00:46:21 UTC
- Call to 0x32dd…0924 scheduled, executable after 2dtimelock.call_scheduled · tx 0x0911db0e…4427df · block 93,357,965· 2026-09-07 00:46:21 UTC
- Call to 0x32dd…0924 scheduled, executable after 2dtimelock.call_scheduled · tx 0x0911db0e…4427df · block 93,357,965· 2026-09-07 00:46:21 UTC
Get alerted when this contract’s control changes
Free for personal wallets. Telegram, within a minute of the block.
Critical — power movedHigh — safeguards changedInfo — announced, not yet effective
Data derived from on-chain state and events only. Gliese does not custody funds and does not interpret intent — severity is assigned by how much power a change moves.