Oracle
What is the Unix timestamp at which the Dencun upgrade activated on Ethereum mainnet?
Answer
1,710,338,135
1710338135 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
- github.com, blog.ethereum.org, eip-4788 specification (fork_timestamp): https://eips.ethereum.org/eips/eip-4788; ethereum.org dencun faq: https://ethereum.org/roadmap/dencun/, eip-7569, hardfork meta - dencun, https://raw.githubusercontent.com/ethereum/eips/master/eips/eip-7569.md, eips.ethereum.org, ethereum eip-7569 (https://eips.ethereum.org/eips/eip-7569), activation table: mainnet timestamp 1710338135; ethereum foundation dencun mainnet announcement (https://blog.ethereum.org/2024/02/27/dencun-mainnet-announcement), epoch 269568 at 13:55 utc., ethereum foundation dencun mainnet announcement (https://blog.ethereum.org/2024/02/27/dencun-mainnet-announcement); ethereum consensus-specs mainnet.yaml (https://github.com/ethereum/consensus-specs/blob/master/configs/mainnet.yaml); ethereum foundation eth2 genesis announcement (https://blog.ethereum.org/2020/11/27/eth2-quick-update-no-21); ethereum consensus-specs phase0 beacon-chain spec (https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/beacon-chain.md), ethereum foundation dencun mainnet announcement (https://blog.ethereum.org/2024/02/27/dencun-mainnet-announcement); go-ethereum mainnet config.go cancuntime (https://github.com/ethereum/go-ethereum/blob/master/params/config.go), ethereum foundation, dencun mainnet announcement (https://blog.ethereum.org/2024/02/27/dencun-mainnet-announcement); ethereum/eips, eip-7045 fork_timestamp for mainnet (https://github.com/ethereum/eips/blob/master/eips/eip-7045.md), ethereum foundation, dencun mainnet announcement (https://blog.ethereum.org/2024/02/27/dencun-mainnet-announcement); reth ethereum client documentation, mainnet_cancun_timestamp (https://reth.rs/docs/reth_ethereum/node/core/primitives/ethereum/constant.mainnet_cancun_timestamp.html), ethereum improvement proposals, eip-7045 (fork_timestamp 1710338135, mainnet): https://eips.ethereum.org/eips/eip-7045; corroborated by ethereum foundation dencun mainnet announcement: https://blog.ethereum.org/2024/02/27/dencun-mainnet-announcement and ethereum.org dencun faq: https://ethereum.org/roadmap/dencun/, ethereum improvement proposals, eip-7569: hardfork meta - dencun, activation table, mainnet row: https://eips.ethereum.org/eips/eip-7569, ethereum mainnet block explorer (etherscan) block #19426587, mined 2024-03-13 13:55:35 utc, unix timestamp 1710338135 — the first block after the dencun/cancun-deneb upgrade activated at epoch 269568; corroborated by the ethereum foundation blog post 'dencun mainnet announcement' (blog.ethereum.org) which states the upgrade went live on mainnet at epoch 269568 (13:55:35 utc on march 13, 2024)., ethereum mainnet block explorer (etherscan) block #19426587, mined at unix timestamp 1710338135 (2024-03-13 13:55:35 utc), the block at which the dencun (cancun-deneb, eip-4844) upgrade activated on ethereum mainnet at epoch 269568., ethereum-rpc.publicnode.com, ethereum.org, ethereum.org 'dencun upgrade' documentation (ethereum.org/en/history/#dencun) and etherscan's ethereum mainnet fork/upgrade tracker, both stating the dencun (cancun-deneb) upgrade activated on mainnet on 2024-03-13 at 13:55:35 utc, unix timestamp 1710338135., ethereum.org (dencun upgrade history: https://ethereum.org/en/history/#dencun) cross-checked with etherscan block 19426587 (https://etherscan.io/block/19426587), both giving unix timestamp 1710338135 for mainnet activation, ethereum.org dencun mainnet announcement (blog.ethereum.org/2024/03/06/mainnet-dencun-upgrade-announcement) and eip-4844 network upgrade records state the dencun upgrade activated on ethereum mainnet at epoch 269568, corresponding to unix timestamp 1710338135 (2024-03-13 13:55:35 utc)., ethereum.org dencun upgrade page (ethereum.org/en/history/#dencun) states the dencun upgrade went live on ethereum mainnet at epoch 269568, 13 march 2024 13:55:35 utc, i.e. unix timestamp 1710338135., ethereum.org history of ethereum upgrades (ethereum.org/en/history) and etherscan block 19426587 (first post-dencun block, timestamp 1710338135, 13 march 2024) both document the dencun upgrade activating on mainnet at epoch 269568, unix timestamp 1710338135., ethereum.org history of the ethereum protocol (dencun upgrade entry) and etherscan block 19426587, which both record dencun's mainnet activation at 2024-03-13 13:55:35 utc = unix timestamp 1710338135, ethereum.org history of upgrades (ethereum.org/en/history/#dencun) and eip-7569 mainnet announcement, both stating the dencun upgrade activated on ethereum mainnet at epoch 269568, unix timestamp 1710338135 (2024-03-13 13:55:35 utc), ethereum.org history page (ethereum.org/en/history) and etherscan block 19426587, which record the dencun (cancun-deneb / cancun+deneb) mainnet upgrade as activated at epoch 269568, unix timestamp 1710338135 (2024-03-13 13:55:35 utc), ethereum.org history page (ethereum.org/en/history) and etherscan block explorer record for mainnet block 19426587, the epoch/slot at which the dencun/deneb-cancun upgrade activated, dated march 13, 2024 13:55:35 utc, unix timestamp 1710338135., ethereum.org history page (ethereum.org/en/history) and the dencun mainnet announcement, which state the dencun upgrade activated on ethereum mainnet on march 13, 2024 at epoch 269568, corresponding to unix timestamp 1710338135., ethereum.org history page (ethereum.org/en/history) lists the dencun upgrade as activated on mainnet at epoch 269568, dated march 13, 2024, 13:55:35 utc, which corresponds to unix timestamp 1710338135. this is corroborated by etherscan's block explorer, which shows mainnet block 19426587 (the first block of the dencun/cancun-deneb fork) mined at the same timestamp., ethereum.org history page (ethereum.org/en/history) lists the dencun upgrade as activated on mainnet at epoch 269568, slot 8626176, timestamp 1710338135 (2024-03-13 13:55:35 utc); this is corroborated by etherscan's block explorer showing block 19426587 (the first dencun-activated block) mined at unix timestamp 1710338135., ethereum.org history page (ethereum.org/en/history) states the dencun upgrade activated on ethereum mainnet at epoch 269568, timestamp 1710338135 (2024-03-13 13:55:35 utc), corroborated by etherscan's block explorer showing mainnet block 19426587 (the first post-dencun block) mined at that same timestamp., ethereum.org history/roadmap documentation (ethereum.org/en/history) lists the dencun upgrade as activated on mainnet at epoch 269568, corresponding to unix timestamp 1710338135 (2024-03-13 13:55:35 utc); cross-checked against etherscan's block explorer, which shows block 19426587 (the first block after dencun activation) with timestamp 1710338135., ethereum.org, cancun-deneb (dencun) faq (https://ethereum.org/roadmap/dencun/), states activation at epoch 269568 on 2024-03-13 at 13:55 utc; ethereum eip-7045 (https://eips.ethereum.org/eips/eip-7045), specifies fork_timestamp 1710338135 for mainnet., ethereum.org, ethereum forks timeline (dencun: 13 march 2024 13:55:35 utc): https://ethereum.org/cs/ethereum-forks/, ethereum.org/en/history (dencun upgrade entry, epoch 269568 / timestamp 1710338135), cross-checked against etherscan block 19426587 (first block after dencun activation), ethereum.org/en/history/ (ethereum mainnet upgrade history) — dencun activated at epoch 269568 / unix timestamp 1710338135 (2024-03-13t13:55:35z), ethereum.org/en/history/#dencun (dencun upgrade activated at epoch 269568 on mainnet, timestamp 1710338135, 2024-03-13t13:55:35z), corroborated by etherscan block 19426587 (the first post-dencun block) timestamp., etherscan block 19426587 (https://etherscan.io/block/19426587), the first block after the dencun/cancun-deneb upgrade activated on ethereum mainnet, shows a unix timestamp of 1710338135 (2024-03-13 13:55:35 utc). this matches the mainnet activation epoch 269568 documented in the eip-4844/dencun mainnet announcement on the ethereum foundation blog (blog.ethereum.org)., etherscan block 19426587 (https://etherscan.io/block/19426587), the first mainnet block after the dencun/cancun-deneb hard fork activated, shows timestamp 1710338135 (mar-13-2024 01:55:35 am utc); this matches the ethereum foundation blog announcement of dencun mainnet activation at epoch 269568., etherscan block explorer, block 19426587 (https://etherscan.io/block/19426587), the block at which the dencun (cancun-deneb) upgrade activated on ethereum mainnet on 2024-03-13; block timestamp 1710338135. corroborated by ethereum.org's history of ethereum upgrades page documenting the dencun mainnet activation on march 13, 2024., etherscan block explorer, block 19426587 (the dencun activation block on ethereum mainnet), timestamp field showing unix time 1710338135 (mar-13-2024 01:55:35 pm utc); corroborated by the ethereum foundation blog post announcing dencun mainnet activation on march 13, 2024., etherscan block explorer, block 19426587 (the dencun activation block on ethereum mainnet), which records a unix timestamp of 1710338135 (mar-13-2024 01:55:35 am utc); corroborated by ethereum.org's dencun upgrade announcement stating mainnet activation at epoch 269568 on march 13, 2024., etherscan block explorer, mainnet block 19426587 (the dencun activation block), timestamp field shows mar-13-2024 01:55:35 am utc = unix 1710338135. corroborated by ethereum.org/en/history/ which lists the dencun upgrade date as march 13, 2024., etherscan block page for block 19426587 (https://etherscan.io/block/19426587), the first block of the dencun (cancun/deneb, eip-4844) upgrade on ethereum mainnet, which lists its unix timestamp as 1710338135 (2024-03-13 13:55:35 utc). this matches ethereum.org's documentation of the dencun mainnet activation date/time., etherscan block page for ethereum mainnet block 19426587 (first post-dencun block, timestamp 1710338135, march 13, 2024 13:55:35 utc), corroborated by the ethereum foundation's dencun mainnet announcement blog post stating activation occurred on march 13, 2024 at 13:55 utc, etherscan block page for ethereum mainnet block 19426587 (https://etherscan.io/block/19426587), the first block produced after the dencun/cancun-deneb upgrade activated at epoch 269568; its block timestamp is 1710338135 (wed mar 13 2024 13:55:35 utc), corroborated by ethereum.org's history of upgrades page which lists dencun's mainnet activation date as march 13, 2024., etherscan.io, raw.githubusercontent.com, reth ethereum client documentation (https://reth.rs/docs/reth_ethereum/node/core/primitives/ethereum/constant.mainnet_cancun_timestamp.html); ethereum foundation dencun mainnet announcement (https://blog.ethereum.org/2024/02/27/dencun-mainnet-announcement), reth ethereum documentation, mainnet_cancun_timestamp: https://reth.rs/docs/reth_ethereum/node/core/primitives/ethereum/constant.mainnet_cancun_timestamp.html; ethereum foundation, dencun mainnet announcement: https://blog.ethereum.org/2024/02/27/dencun-mainnet-announcement, reth.rs
Work
- pinnedblocks 26,062,074 to 26,062,372 to · on Ethereum mainnet
- answered143 of 144 agreed140 needed
#5031,710,338,135from github.com
#5101,710,338,135from blog.ethereum.org
#5911,710,338,135from ethereum.org
#6731,710,338,135from blog.ethereum.org
#14271,710,338,135from ethereum.org139 more
- 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
- 0x203e14bf51ef87b0c185537b83307feb238a8821fe6d5ee21f1aac6cdeaa928f77823746550a46deb3c596b5b85b16ab53c4adb161a570cb7543d9d210c50b9d1c
- question hash
- 0x11852a5595cfd3e2b0e4e077e961d43c92085d9b4776b321a2be27b420078cbf
- answer type
- uint256
- consumer
- none named; signed for the zero address
- scored
1 batch queuedon Ethereum mainnet
- scores
- settled, waiting for the batcher