Block
#21716680
Status:
Finalized
Timestamp:
393 days ago (Jan-27-2025 03:12:59 PM +UTC)
Transactions:
468 transactions and 100 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.105895989827451147 ETH (0 + 0.707395243264420937 - 0.60149925343696979)
Total Difficulty:
0
Size:
135,588 bytes
Gas Used:
29,998,121 (99.32%)
Gas Limit:
30,204,807
Base Fee Per Gas:
0.00000002005123099 ETH (20.05123099 Gwei)
Burnt Fees:
š„ 0.60149925343696979 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,181.65 / ETH
Hash:
0xdf48348ecc538382a87be9ca4db034bffdcdc0f15eef22e87a685cbc97e6a11b
StateRoot:
0xc1a5f235bc1342fa8535b071c8c0e7f2ef9d3d87fc8246db3140839a4022dc7f
WithdrawalsRoot:
0x4f7442c1015ad86663cab9d0ecd716d706eda96fbaf3ffd6701af61b1230d543
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xb468bdb6ee3f0d4cb82341b3d881707348a1f30b04c8c593ef0ff4b107bd7298
Parent Root Hash:
0x540cf2e063837bd6acf0bff4ad456a24fe2aaebc2b3c854c04f7aa5f7add55b5
Beacon Chain Deposit Count:
1885213
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xb28c26eec0dddd61b306e4aa4fab5eb26a5ef1fa24489e2c1d3a806fc519bad5
Randao Reveal:
0xb19307eda43ca1d18ecc593f093af81d60be20892c33d0e75b2779ae3cc1b033201180dfa6307f3eb27f56aa1579e88000ccbedd647808e312a2729a8dacff17316979ae281aaf5780d956eb8e8ae9cd762038e356ef19fc72dd21cd4fa49e26
Proposer Fee Recipient:
0x51a1449b3B6D635EddeC781cD47a99221712De97 (Fee Recipient: 0x51...e97)
MEV Reward:
0.118041909215322442 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
384 KiB (3 blobs)
Blob Utilisation:
3 Blobs (50.00%)
Blob Gas Price:
0.000000017002220575 ETH (17.002220575 Gwei)
Blob Gas Used:
393,216 (50.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.0066855451656192 ETH
Excess Blob Gas:
78,643,200 (600 blobs)
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.