Contract control history
Safe on Ethereum — who can change it, and what changed
Upgradeable by a single keySafe 1 of 5: one signature is enough
This Safe safe at 0xa633…8f5b on Ethereum is controlled by a 1-of-5 Safe. Gliese has recorded 2 control changes and 3 deployment-time events. Last checked 2026-09-09 13:12:08 UTC.
Current control surface
snapshot 2026-09-09 12:06:39 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Safe threshold
- 1 of 5signatures required to act
- Safe owners · 1 of 5
Recorded events
Open in the feed →| Event | Real | Setup |
|---|---|---|
| Added ownersafe.added_owner | 2 | 1 |
| Enabled modulesafe.enabled_module | 0 | 1 |
| Setupsafe.setup | 0 | 1 |
| Total | 2 | 3 |
Recent changes
Setup-time events hidden- Signer 0xe490…d271 added to the Safesafe.added_owner · tx 0xb7a6f82f…268242 · block 25,939,582· 2026-09-09 11:41:23 UTC
- Signer 0x8394…f0b1 added to the Safesafe.added_owner · tx 0x9e1888e2…78169e · block 25,939,555· 2026-09-09 11:35:59 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.