Block
#21169305
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
471 days ago (Nov-12-2024 04:46:11 AM +UTC)
Transactions:
134 transactions and 62 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.033810749695162996 ETH (0 + 0.278183696170760262 - 0.244372946475597266)
Total Difficulty:
0
Size:
49,426 bytes
Gas Used:
12,146,941 (40.49%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000020118064826 ETH (20.118064826 Gwei)
Burnt Fees:
š„ 0.244372946475597266 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,256.98 / ETH
Hash:
0x5b255ac47427bd602d8c68b7db7dc80f98c2c83deb78da031f17cf30d3f3c17c
StateRoot:
0x8e58987416c000279d687872ffb8f98f8ec97892ab2c005039edb87d25460eab
WithdrawalsRoot:
0x6871e432d34e27336bdcd026f227cf9be8d35a4342f682800b0772e4a352ddd3
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x764cf3729227c59c13bab7fa1a75d4f7795e76cf7b49405c35696f262c8ebc83
Parent Root Hash:
0xe7a80ce4836e04e47953587369b5dfea40cd59754fd952624fa093d6a27c6436
Beacon Chain Deposit Count:
1765697
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x08ff913d2ea36446ac313f41e697365761f3fc7d434d8d82516ba48d43bb6d9e
Randao Reveal:
0x8023500984eaea5d9c7687b5bee94fd73684525829d3f4a6c4f77f6d5220001eb6da4607d24b8ca6f89effaa6ebc268f008c196c38965659bd349cece0568d955c5f68ca70f7244e4bf0ce9263ac8dde739c875ff3859166d49b4c890326e8e4
Proposer Fee Recipient:
0x7D16d2c4e96BCFC8f815E15b771aC847EcbDB48b (Liquid Collective: Fee Recipient)
MEV Reward:
0.14497500598553226 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6 Blobs (100.00%)
Blob Gas Price:
0.000000022380075395 ETH (22.380075395 Gwei)
Blob Gas Used:
786,432 (100.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.0176004074530406 ETH
Excess Blob Gas:
79,560,704 (607 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.