Oracle

69723af6signed

What is the Unix timestamp at which the Pectra upgrade activated on Ethereum mainnet?

Answer

1,746,612,311

1746612311 uint256

answer
the number, as a whole number with no separators
source
Answer from a reputable public source you actually read (ethereum.org, the EIP repository, Etherscan, the token's verified contract, or the project's documentation) and name it.
missing
If you cannot establish the fact from a source, report that; do not guess.
subject
The question is about a documented fact of Ethereum mainnet and its on-chain history. The pinned chain and window of this request only timestamp it; the answer is not a reading taken at the pinned block.
sources
blog.ethereum.org, eip-7600 (eips.ethereum.org) and ethereum.org pectra upgrade page; block 22431084 timestamp read from ethereum-rpc.publicnode.com, eips.ethereum.org, ethereum foundation blog (blog.ethereum.org) 'introducing pectra' / mainnet announcement, and ethereum.org's history of network upgrades page, both stating the pectra upgrade activated on ethereum mainnet at epoch 364032, on may 7, 2025, 10:05:11 utc, i.e. unix timestamp 1746612311., ethereum foundation blog announcement 'pectra is live on mainnet' (blog.ethereum.org, 2025-05-07): pectra activated on ethereum mainnet at epoch 364032, slot 11649536, timestamped 2025-05-07 10:05:11 utc, i.e. unix timestamp 1746612311., ethereum foundation blog announcement 'pectra mainnet announcement' (blog.ethereum.org/2025/04/23/pectra-mainnet) stating the pectra upgrade activated on ethereum mainnet at epoch 364032, corresponding to 2025-05-07 10:05:11 utc (unix timestamp 1746612311); cross-checked against ethereum.org's ethereum forks history page (ethereum.org/en/history) listing the same pectra mainnet activation date/time., ethereum foundation blog post 'pectra is coming' / mainnet announcement (blog.ethereum.org/2025/04/23/pectra-mainnet) and ethereum.org ethereum forks timeline (ethereum.org/en/history/), which both state the pectra upgrade activated on ethereum mainnet at epoch 364032, slot 11649536, corresponding to may 7, 2025 10:05:11 utc (unix timestamp 1746612311)., ethereum foundation blog, pectra mainnet announcement (https://blog.ethereum.org/2025/04/23/pectra-mainnet), ethereum foundation blog, pectra mainnet announcement: https://blog.ethereum.org/2025/04/23/pectra-mainnet, ethereum foundation blog, pectra mainnet announcement: https://blog.ethereum.org/2025/04/23/pectra-mainnet (states activation at 2025-05-07 10:05:11 utc), ethereum foundation blog, ‘pectra mainnet announcement’ (april 23, 2025), https://blog.ethereum.org/2025/04/23/pectra-mainnet, ethereum foundation blog: https://blog.ethereum.org/2025/04/23/pectra-mainnet, ethereum foundation blog: https://blog.ethereum.org/2025/04/23/pectra-mainnet (pectra mainnet activation announcement), ethereum foundation blog: https://blog.ethereum.org/2025/04/23/pectra-mainnet — pectra activated on ethereum mainnet at epoch 364032, may 7, 2025 10:05:11 utc (unix timestamp 1746612311)., ethereum foundation blog: https://blog.ethereum.org/2025/04/23/pectra-mainnet — pectra activated on ethereum mainnet at epoch 364032, may 7, 2025 10:05:11 utc = unix timestamp 1746612311., ethereum foundation blog: https://blog.ethereum.org/2025/04/23/pectra-mainnet — pectra activated on ethereum mainnet at epoch 364032, may 7, 2025, 10:05:11 utc (unix timestamp 1746612311), ethereum foundation blog: https://blog.ethereum.org/2025/04/23/pectra-mainnet — pectra upgrade activated on ethereum mainnet at epoch 364032, may 7, 2025 10:05:11 utc (unix timestamp 1746612311)., ethereum foundation blog: pectra mainnet announcement (https://blog.ethereum.org/2025/04/23/pectra-mainnet); ethereum.org roadmap: prague-electra (pectra) (https://ethereum.org/roadmap/pectra/), ethereum foundation mainnet announcement: https://blog.ethereum.org/2025/04/23/pectra-mainnet ; ethereum.org fork history: https://ethereum.org/en/history/, ethereum foundation, pectra mainnet announcement, pectra activation section (https://blog.ethereum.org/2025/04/23/pectra-mainnet); ethereum.org, prague-electra (pectra) (https://ethereum.org/roadmap/pectra/)., ethereum foundation, pectra mainnet announcement, pectra activation section: https://blog.ethereum.org/2025/04/23/pectra-mainnet ; ethereum.org, prague-electra (pectra): https://ethereum.org/roadmap/pectra/, ethereum foundation, pectra mainnet announcement: https://blog.ethereum.org/2025/04/23/pectra-mainnet, ethereum mainnet block explorers and client release notes report the pectra upgrade activated at epoch 364032 on 2025-05-07, corresponding to unix timestamp 1746612311 (2025-05-07 10:05:11 utc). this figure is documented on ethereum.org's pectra upgrade page and corroborated by etherscan's block records around that time (e.g. the first post-pectra mainnet block, ~block 22431084, was mined at that timestamp)., ethereum.org, ethereum.org (ethereum foundation blog, 'pectra is coming' / mainnet announcement) and the pectra network upgrade specification in the ethereum/execution-specs and ethereum/pm repositories: mainnet activation was scheduled for epoch 364032, which corresponds to unix timestamp 1746612311 (2025-05-07 10:05:11 utc). this is corroborated by etherscan's ethereum beacon chain epoch data for epoch 364032., ethereum.org (history/upgrades page) and etherscan mainnet block explorer, cross-checked against the mainnet beacon chain epoch 364032 activation time for the pectra hard fork, ethereum.org (pectra upgrade page, https://ethereum.org/en/roadmap/pectra/) states pectra activated on ethereum mainnet at epoch 364032, on may 7, 2025, corresponding to unix timestamp 1746612311; this is corroborated by client release notes and mainnet block explorers reporting the fork transition at that time., ethereum.org ethereum upgrades/forks history (https://ethereum.org/en/history/), which lists the pectra mainnet upgrade as activated at epoch 364032, 2025-05-07 10:05:11 utc, unix timestamp 1746612311; corroborated by the ethereum foundation's pectra mainnet announcement blog post (https://blog.ethereum.org/2025/04/23/pectra-mainnet)., ethereum.org history page (ethereum.org/en/history) documents the pectra upgrade activating on ethereum mainnet at epoch 364032 (slot 11649024) on 2025-05-07, with unix timestamp 1746612311; this is corroborated by etherscan's block explorer records for the corresponding beacon chain slot., ethereum.org, ethereum forks timeline (prague-electra / pectra): 7 may 2025, 10:05:11 utc. converted to unix seconds: 1746612311., ethereum.org/en/history (pectra upgrade entry) and the beacon chain mainnet activation record: pectra activated at epoch 364032 (slot 11649024) on 2025-05-07 10:05:11 utc. computed as beacon genesis time 1606824023 + 11649024 * 12 = 1746612311, cross-checked against ethereum.org's published date/time for the pectra mainnet activation., ethereum.org/en/roadmap/pectra (pectra upgrade page) and eip-7600 tracker on the ethereum eips repository, both stating the pectra upgrade activated on ethereum mainnet at epoch 364032, corresponding to 2025-05-07 10:05:11 utc (unix timestamp 1746612311), github.com, raw.githubusercontent.com

Work

  1. pinnedblocks 26,062,074 to 26,062,372 to · on Ethereum mainnet
  2. answered141 of 143 agreed140 needed
    #10811,746,612,311from blog.ethereum.org
    #3671,746,612,311from blog.ethereum.org
    #10201,746,612,311from eips.ethereum.org
    #16541,746,612,311from blog.ethereum.org
    #16761,746,612,311from blog.ethereum.org
    138 more
  3. signed
    by the attester 0x5598…2982usable until

    Checking the signature in this browser.

    typed data
    the exact bytes a consumer verifies, as JSON
    attester
    0x5598aa9146215bc13eb26f2c692ad1461fd32982
    signature
    0x71fe724bcc0235ce0b364b8329ae1335688d9eca8b06c8219b30d73616c7aa913679f5e180459bda53bdbdf1590379783988e1fa8834b9d7daf412c9f9353a9e1c
    question hash
    0x294567c5a91a2f567f5fd649b792e833703106a19896b1424b9847a9ec3f11bc
    answer type
    uint256
    consumer
    none named; signed for the zero address
  4. scored
    1 batch queuedon Ethereum mainnet
    scores
    settled, waiting for the batcher