Block
#20160677
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
608 days ago (Jun-24-2024 09:34:23 AM +UTC)
Transactions:
132 transactions and 44 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.055418351938848141 ETH (0 + 0.25699830245092398 - 0.201579950512075839)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
77,281 bytes
Gas Used:
15,889,269 (52.96%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000012686546531 ETH (12.686546531 Gwei)
Burnt Fees:
š„ 0.201579950512075839 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,350.54 / ETH
Hash:
0xabb986d40bff6a3851c308e9b96d30826920139fc121213c2d0f5e7c225560d4
StateRoot:
0xb6aca70edf3800d18c474f75e67b700611a7bde37d77c2ddb2837b71a2a4f698
WithdrawalsRoot:
0xc29ee47393335e7c0242af6cdfc2c885b560e6e980167bf4cd065c1c57d13ba8
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x81900cc1bf413c62da14fd486a15869d89b6ec2147047bb9f3f6b4a2b78dd095
Parent Root Hash:
0x5ce53c20f0b0b21d3855bb4b7de7d1f19cee2fc78fa6273ed14c5a76028d0bd0
Beacon Chain Deposit Count:
1555155
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xa4d62de1d5158bc2056b7d2695e964a8d0ebb0450b202a31a3efd324e67db7c0
Randao Reveal:
0x84861c57093bc22f63129bcbba91dde03bb42ea6bf7721c24f4af295cdbb4034b38b794187c79e2ebc6685f7db2d672b152d29ae48293cc3c2e94823107a258161cd366f636711bdfca48a25a7e33347ed0434cf870f7f069c68d323b8a3cacc
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.249261273213400373 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
640 KiB (5 blobs)
Blob Utilisation:
5 Blobs (83.33%)
Blob Gas Price:
19 wei (0.000000019 Gwei)
Blob Gas Used:
655,360 (83.33%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.00000000001245184 ETH
Excess Blob Gas:
9,961,472 (76 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.