Block
#20134172
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
613 days ago (Jun-20-2024 04:36:47 PM +UTC)
Transactions:
168 transactions and 40 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.074679727573836179 ETH (0 + 0.244759561055488102 - 0.170079833481651923)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
61,761 bytes
Gas Used:
11,870,917 (39.57%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000014327438519 ETH (14.327438519 Gwei)
Burnt Fees:
š„ 0.170079833481651923 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$3,510.94 / ETH
Hash:
0x36f8f029bb19bd7e657c51d55b1187069cf3814d972a905292c9e7422c1d2e75
StateRoot:
0xa8227f2425378af8ef34500c9234bd825f5f357776e45ed6ad6ef8b355b1e02c
WithdrawalsRoot:
0xe58ba93c6ef471da7f5cf0c95d3083998b8c3b929b90eff641d05571afeaff90
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xf34e022da33dd5e35e2aa43d661baa1b140afc37633452e375588b44e7313671
Parent Root Hash:
0xc5fc0b5ade690188232a54a0c472a90264a7312f766bbf1355b87cf9d58039c6
Beacon Chain Deposit Count:
1547493
Slot Graffiti:
Nethermind for Lido TKcdcb (Hex:0x4e65746865726d696e6420666f72204c69646f20544b63646362000000000000)
Block Randomness:
0x81246971aaebf59c3cd20d9f0494e052ad662974722eeb34e92bf7770f255866
Randao Reveal:
0x91570559d3e349f7aeca54c881fa63cdb2b7a1e278b270ed6f43af93b4cd442d1cfd6194c757a69be5327977a221cfe51901b2e1cac96088ac99fdb64ceef3ea45d1ef07771b1d87ad7065817ac9ac9dd98e8442d3e70bd2d7fa178be660399e
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.10869972413326593 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.