Block
#20460065
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
573 days ago (Aug-05-2024 04:46:11 AM +UTC)
Transactions:
107 transactions and 60 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.020392992665197813 ETH (0 + 0.219936078055189861 - 0.199543085389992048)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
38,482 bytes
Gas Used:
8,698,972 (29.00%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000022938697284 ETH (22.938697284 Gwei)
Burnt Fees:
🔥 0.199543085389992048 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,420.39 / ETH
Hash:
0x1fd8d2110b1180272b3ba07d2e40fdeae1f6b2c5cc9e194f8b051216ae961ced
StateRoot:
0x4bc0c6a590bdadc61e79d872a86b7fd1a00f2202137327b5bdb4e9cbf3014a9b
WithdrawalsRoot:
0x3954470d963366d191a17e68ea3e2d8592d1fae1cf1cf2583529e2ff6223deda
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x72c94e5bf7ab0e2e861b34135e9c6932db902aa0617a5467235c5bc7bdefb6d2
Parent Root Hash:
0x62fb8653fad4a638dea5695d63576e39e62851c1aa03f4690707d8ceab634545
Beacon Chain Deposit Count:
1627254
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xb154f3b6a2212c846cd766de0fc8ab9e41c6ce6c65d729e1ad4dfeda27452390
Randao Reveal:
0xb823eb3c2e3da7c00d2e61180630c350183fefaefdcb03659051775c32165224024352ceef9860033f74b559bf9d451d0c0d62188b93eb9e9805ee203a8f0d37d3a74da583e6c1a0245f1913f0a086e249ba4f3f9002443dd49a1a06ab442d61
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.050294368165771883 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.