Explorer ↗Watch this contract
Contract control history

LombardTimeLock on Ethereum — who can change it, and what changed

Multisig + 24h+ timelockthis contract is a timelock with a 1d minimum delay

This timelock at 0x055e…⁠7e59 on Ethereum sits behind a 1d timelock. Gliese has recorded 5 control changes. Last checked 2026-09-12 20:43:34 UTC.

Timelock1d timelockEthereum

Current control surface

snapshot 2026-09-11 20:19:44 UTC
Implementation
EIP-1967 logic contract; an upgrade changes this
Proxy admin
who can upgrade
Owner
owner()
Timelock delay
1d
minimum wait between queue and execution

Recorded events

Open in the feed →

Recent changes

Setup-time events hidden
  1. Scheduled call to 0x9646…⁠3fc0 executed
    timelock.call_executed · tx 0x1e8962fe…⁠38ca4f · block 25,966,992
    · 2026-09-13 07:23:35 UTC
  2. Call to 0x451c…⁠0a2d scheduled, executable after 1d
    timelock.call_scheduled · tx 0x34886d94…⁠16a7de · block 25,966,989
    · 2026-09-13 07:22:59 UTC
  3. Call to 0x451c…⁠0a2d scheduled, executable after 1d
    timelock.call_scheduled · tx 0x34886d94…⁠16a7de · block 25,966,989
    · 2026-09-13 07:22:59 UTC
  4. Call to 0x451c…⁠0a2d scheduled, executable after 1d
    timelock.call_scheduled · tx 0x34886d94…⁠16a7de · block 25,966,989
    · 2026-09-13 07:22:59 UTC
  5. Call to 0x9646…⁠3fc0 scheduled, executable after 1d
    timelock.call_scheduled · tx 0xfee63820…⁠feb40c · block 25,956,503
    · 2026-09-11 20:18:47 UTC
Full history since deployment →
Get alerted when this contract’s control changes
Free for personal wallets. Telegram, within a minute of the block.
Criticalpower movedHighsafeguards changedInfoannounced, 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.