Block
#19807589
Status:
Finalized
Timestamp:
270 days ago (May-06-2024 12:52:11 AM +UTC)
Transactions:
189 transactions and 106 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.01347908623544319 ETH (0 + 0.089632654127415352 - 0.076153567891972162)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
88,263 bytes
Gas Used:
17,642,701 (58.81%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000004316434762 ETH (4.316434762 Gwei)
Burnt Fees:
š„ 0.076153567891972162 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,063.19 / ETH
Hash:
0xd10dacaca8a4ce12888ee3bebfdbf3e88b1de0f76f8a654e406d77b63dae5701
StateRoot:
0xd26d4b930e3cf8c3c72ad2262dad5a6f8eb13efc38e26085fc22e069e3334de3
WithdrawalsRoot:
0x0583540bf3afa183de0ddc0a4b30971530238913cd739ccec288ed07feaa1b41
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xe4d14b435d064db913ebb8a7ea2d401e12c3c09665485b9fb8d381fc5455d396
Parent Root Hash:
0xe6c07d55d56fc7c173ac93449026b793e8b621a69f4104ecd74c1e76f46e1fc3
Beacon Chain Deposit Count:
1464215
Slot Graffiti:
Block by Stakely Lido008 TK (Hex:0x426c6f636b206279205374616b656c79204c69646f30303820544b0000000000)
Block Randomness:
0x1983d3c59638a5e1162f6f93797387c5e34c893e061be35e430c360ef3131f01
Randao Reveal:
0x84f23df3a2a27cd5b810714fdf5886978143826d7b85193bc01c6ab6471787300edc71f94649948ec3a1145c65d536c808dee7ce499aa6e4e70597dcb2d9db275d7f0ab1ce41819ca8b446a678f3dc1a26577f014efd80670647cde750ad6977
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.01958078611828767 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
128 KiB (1 blobs)
Blob Utilisation:
1.00 Blobs (16.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
131,072 (16.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.