Status:
Finalized
Timestamp:
315 days ago (May-25-2024 03:56:11 AM +UTC)
Transactions:
155 transactions and 53 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.017780196039792578 ETH (0 + 0.064362779878044878 - 0.0465825838382523)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
70,781 bytes
Gas Used:
12,736,314 (42.45%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.00000000365746195 ETH (3.65746195 Gwei)
Burnt Fees:
š„ 0.0465825838382523 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,749.23 / ETH
Hash:
0xaea5676f130770c5b071975d4ece5376b14e2df981f25e8a2572f656ccedb94f
StateRoot:
0x21b06e3764fea2f850d83536df5092d10b5e954a9e431e9684606d31d32fc69e
WithdrawalsRoot:
0x796aabff295a984ed50cae1c450471df09f34920b75605f69552bcaca89a5b63
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x1d994b31bf05d811bd5d5821fd787f779bb219e250bbabc9d3d318531d1b1aff
Parent Root Hash:
0xc7396034677dd4b1ee8c488e77cf0c01b62a075e40e2f0fdb022f4b81f9e87f0
Beacon Chain Deposit Count:
1487986
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xaae2c0cac7f26b2821157815e4f3fc092a03d03f911aef59d030161685cda449
Randao Reveal:
0x86efb634bbe5c425bd47413daeb4eff4bac9d8dabd9d3bdff3581ed921486a313e8aa18ae8c81b77d3b4004f32e983bc194e9746e8f7293d9999bc68efa8978b90e1ad1814d384ee6d36bb9357b6a73fcc5bcf2091240dffda77dbcd737417c1
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.017655796707980973 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
512 KiB (4 blobs)
Blob Utilisation:
4.00 Blobs (66.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
524,288 (66.67%)
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.