Block
#19969856
Status:
Finalized
Timestamp:
233 days ago (May-28-2024 05:27:59 PM +UTC)
Transactions:
172 transactions and 74 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Flashbots: Builder 2 in 12 secs
Block Reward:
0.193784765141319808 ETH (0 + 0.425413965109043029 - 0.231629199967723221)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
68,344 bytes
Gas Used:
14,184,059 (47.28%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000016330247919 ETH (16.330247919 Gwei)
Burnt Fees:
š„ 0.231629199967723221 ETH
Extra Data:
Illuminate Dmocratize Dstribute (Hex:0x496c6c756d696e61746520446d6f63726174697a6520447374726962757465)
Ether Price:
$3,840.39 / ETH
Hash:
0x0a140fe14c9b3e2681805a604a0e2003f4458a5bb58fbca52f649e059086b38d
StateRoot:
0x9f1555acf0b02fda8bff4d764f23293beba2785386c58090f737f558527bdad8
WithdrawalsRoot:
0x3919b6f581fe51d9aae3e1954777edad9360e53958cee27228f4918830562cd0
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x3f58cdb794ce4012b8377cbb62cb2f1292216832d18ee203b5f56fdfefb223ae
Parent Root Hash:
0xdb4fc434cf956d36fc276588d8a71d462a0498cb4c023b488fedf5b27f9b4b17
Beacon Chain Deposit Count:
1489867
Slot Graffiti:
Block by Stakely Lido012 TK (Hex:0x426c6f636b206279205374616b656c79204c69646f30313220544b0000000000)
Block Randomness:
0xa54891da53a24020fcf1419bb7de7ebf15469eef4948046b6ca04358b5790498
Randao Reveal:
0x812ecd79f1f6f8d89f0f94fbb3ef922192793e8b015605cc94a2aecb5ab946d3f836d6f1edefec9dc9e84301b809f7c61183818dbf2e576787878ca4431f7de62fd5a085cd3d61ab35fabe6feb0e6233bac64654e897e11b1cf3ce9748ea2aad
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.306738693174123254 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
Blob Utilisation:
Blob Gas Price:
Blob Gas Used:
Blob Gas Limit:
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.