Block
#19610181
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
693 days ago (Apr-08-2024 09:52:47 AM +UTC)
Transactions:
221 transactions and 86 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.188261874124166505 ETH (0 + 0.500125377015876729 - 0.311863502891710224)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
219,022 bytes
Gas Used:
20,482,488 (68.27%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000015225860398 ETH (15.225860398 Gwei)
Burnt Fees:
🔥 0.311863502891710224 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,694.70 / ETH
Hash:
0xf1a95fe9478a90b89e9776a9e134ac329b034fc7287c9c35fb8a74da9c980b01
StateRoot:
0x344e3deaa57845f042247d318c180dd516d83ca158dfc6c648d9f1d8d948f8d7
WithdrawalsRoot:
0x86d6fb27a5630b1f1d42ddeff10ea89d79a9eff9dc8267d9051084343de858d7
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x0b8b2dee91a8bbfd4261c1f0431cf962d791047d3048c1610946cbc2bcfcdcc6
Parent Root Hash:
0x3351fb33217b3c580f6f2ff07ebdeccb4f2281bbea83e570c99aba1f50c323ca
Beacon Chain Deposit Count:
1415097
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x35d0e34abb6448ef64f470e767103724f7585df74fc9c169cfb6582f83bf02e2
Randao Reveal:
0xa747fcb6e9594544272650502877f5fefbb3dc183da2e1a84d58fd98aa43a76e89560fe18605540b994e0dedf402b39719fc16c1d93b5033814256906f32ba871ec3fc7b5c2dfac04b595d1e44eb6f184f93d62f16ec9662c006b3728e83eeb1
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.181504867750892477 ETH
MEV Payout Txn Hash:
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.