ETH Price: $2,060.57 (+6.96%)

Block

#23897571
MEV Block
EigenPhi
Block Height:
23897571
Status:
Finalized
Timestamp:
89 days ago (Nov-28-2025 01:48:47 PM +UTC)
Proposed On:
Block proposed on slot 13126142 , epoch 410191
Transactions:
Withdrawals:
16 withdrawals in this block

Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.037014329603869793 ETH (0 + 0.039137914048358745 - 0.002123584444488952)
Total Difficulty:
0
Size:
170,548 bytes

Gas Used:
33,342,616 (55.57%)
Gas Limit:
60,000,000
Base Fee Per Gas:
0.000000000063689797 ETH (0.063689797 Gwei)
Burnt Fees:
🔥 0.002123584444488952 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,032.20 / ETH
Hash:
0x4224b8d12149f58692826aaa0e700a59e78a08df31c5ac5d3ada18430fec3e19
StateRoot:
0x27802b018ff89bfe5c1c3d124571956aaacd944a16d8199e54aee665e95e8d73
WithdrawalsRoot:
0x76f72c5b5ae380f1abdb8794a943363e8e84c52e6c989582db98df46cc234ba1
Nonce:
0x0000000000000000

Slot:
Epoch:
Proposer Index:

Slot Root Hash:
0xd3b3937340f0c11770b990f8bce5cb83c53994bb70f139d9685fb27c2b702f94
Parent Root Hash:
0xc7a7bb0dc26686c2027eff7f2fb31b9b7a4b1de8c86d01aef9e7948ebb499551
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
Twinstake for Lido (Hex:0x5477696e7374616b6520666f72204c69646f0000000000000000000000000000)
Block Randomness:
0x6c2ed74ac631a0160d616228a58529ea300e2192831c16aa03035e41b3f5275b
Randao Reveal:
0x84bac6df1b77178a62901458ddecfc68ef696fa8bfdd2d0c02e8afc71a66e8cd5fbc3f6f2f996c6855e62e5a368722d20ab13b09bb0ec5f4ee647f384b8e0c3b97b274eecf9872192230b2a024d8893e169c50c4c693b44c7ccb1a41a8ba226f
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.058744520068980774 ETH
Blob Tx:
Blob Size:
Blob Utilisation:
Blob Gas Price:
Blob Gas Used:
Blob Gas Limit:
Total Blob Fees:
Excess Blob Gas:
Reserve Blob Base Fee:

Blocks are batches of transactions linked via cryptographic hashes. Any tampering of a block would invalidate all following blocks as all subsequent hashes would change. Learn more about this page in our Knowledge Base.