Oracle
At what beacon chain epoch did the Dencun (Cancun/Deneb) upgrade activate on Ethereum mainnet?
Answer
269,568
269568 uint256
- answer
- the beacon chain epoch number, as a number
- source
- Answer from a reputable public source you actually read (ethereum.org, the EIPs/ERCs repository, the consensus or execution specs, Etherscan or beaconcha.in, or a major news archive) and name it.
- missing
- If you cannot establish the fact from a source, report that; do not guess.
- subject
- The question is about Ethereum's protocol and history. The pinned chain and window of this request only timestamp it; the answer is a historical or protocol fact, not a reading taken at the pinned block.
- sources
- blog.ethereum.org, beaconcha.in, eips.ethereum.org, ethereum.org, github.com, raw.githubusercontent.com
Work
- Pinnedblocks 26,048,866 to 26,049,165 to on Ethereum mainnet
- Answered70 of 70 agreed70 needed#446269,568from blog.ethereum.org#1427269,568from github.com#1637269,568from blog.ethereum.org#1199269,568from ethereum.org#1965269,568from eips.ethereum.org
65 more
Signedby the attester 0x5598…2982expired
Checking the signature in this browser.
- typed data
- the exact bytes a consumer verifies, as JSON
- attester
- 0x5598aa9146215bc13eb26f2c692ad1461fd32982
- signature
- 0x82394420cdf14a06ba7604bc4d1dd89ad52fc09890c1d2b317d6ffe0830f6c9e79c177d6eb4e557f845dec0ed78bfd9c557c663e65f4bdbefbfc547befadfb041b
- signed panel
- not in this signature; signed before the panel was, under version 1
- question hash
- 0x477f8af51f4138598069326fdd283b09466452d19b1336c49dfa2733a839f6b6
- answer type
- uint256
- consumer
- none named; signed for the zero address
Scored1 batch queuedon Ethereum mainnet
- scores
- written, with no entries recorded on it · block 26,052,006 · transaction