Block
#21976402
Status:
Finalized
Timestamp:
347 days ago (Mar-04-2025 10:06:35 PM +UTC)
Transactions:
266 transactions and 35 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
blockbeelder in 12 secs
Block Reward:
0.184136707494378774 ETH (0 + 0.19797464612934027 - 0.013837938634961496)
Total Difficulty:
0
Size:
98,323 bytes
Gas Used:
16,935,864 (47.09%)
Gas Limit:
35,964,743
Base Fee Per Gas:
0.000000000817078989 ETH (0.817078989 Gwei)
Burnt Fees:
🔥 0.013837938634961496 ETH
Extra Data:
https://blockbeelder.com 🐝 (Hex:0x68747470733a2f2f626c6f636b6265656c6465722e636f6d20f09f909d)
Ether Price:
$2,171.13 / ETH
Hash:
0x466b9135cd3458693c76a9e53f6c00d657028b97529fc73eef714c9b06821f80
StateRoot:
0xd7b593b1fdfc08982f9c502f577ea135634d465e5e79dfd0e616813082629546
WithdrawalsRoot:
0x0a4de7d6d616a9e1c470320e08c15969772840fd8cb58012d0cf583a2bc08a31
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xd0749ca01c4cdd09ee7ffcebd88a3cd104346bc5fba88932cf4f91d81d8f0aba
Parent Root Hash:
0x173e4bda3fcf51a7a7e859a82565f72f2b186c461b47319b6ae5ff66482a26f0
Beacon Chain Deposit Count:
1936510
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xcff4545ff9bb82056fde0a9c21826443a5e8d6bec642a87bff1c0134b4bdb701
Randao Reveal:
0x815d6c44265062f1dcddd2c2e804883a52ee24f15597d1376f9ef6e39f30886e1ace084bc4106e5119e7d30634dfd97d0504f6387ac870355fcb38dc221b2e1c1672e33fee3909d77d89441c263c073f4db8f56762289004c163690967cd930f
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.184118641060852995 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.