Block
#19657857
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
569 days ago (Apr-15-2024 02:12:23 AM +UTC)
Transactions:
128 transactions and 41 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.017659100039986063 ETH (0 + 0.161274205393615051 - 0.143615105353628988)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
270,172 bytes
Gas Used:
15,611,998 (52.04%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000009199021506 ETH (9.199021506 Gwei)
Burnt Fees:
š„ 0.143615105353628988 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,103.00 / ETH
Hash:
0xcec440f5552b37e00acabb5b5f90d36ea600da6bea0e888bbc9731fff077a44e
StateRoot:
0xac26c50cf6e7e7dcc9bdddf70efccca125be403f1a8aa866442cef52f95c6594
WithdrawalsRoot:
0xa5c477966fbed9fbac0b2a80baeef84c593feba7e3bcc3708a64fb10726fadfe
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x4db2780def689da6df647308021e334627c0ea080a5431029d10cc8e19da2fa9
Parent Root Hash:
0x6e9ac68799e00fd27cea4288c37f7f09b116fc3e13bb943c569551aa9d7cfa83
Beacon Chain Deposit Count:
1436768
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x9ceb5bdb94621f80defc889f1fe95ba7f783dd69272d6ef1b1fc87f7274133e7
Randao Reveal:
0xabbfae320e052ea9f3f4e011c091c785643600a2ab857d710ca7c9bc8d74ebdde0e6a66cec165331ef0e5934f26898c708fa28b94caa17f7a034231c8a32366bc2da47538592c361393b937f661becdf5748ecdcb0a9f1879e0a4d2903f4e8c5
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.05581010801516944 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
256 KiB (2 blobs)
Blob Utilisation:
2 Blobs (33.33%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
262,144 (33.33%)
Blob Gas Limit:
786,432
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.