Block
#20654138
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
543 days ago (Sep-01-2024 07:10:11 AM +UTC)
Transactions:
138 transactions and 55 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.021517314451402546 ETH (0 + 0.030031078673239881 - 0.008513764221837335)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
63,962 bytes
Gas Used:
12,986,803 (43.29%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000000655570445 ETH (0.655570445 Gwei)
Burnt Fees:
🔥 0.008513764221837335 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$2,426.06 / ETH
Hash:
0x32fef7a87dea172b148a49852729d56c4be1bf6989043fc6187aed957b73b168
StateRoot:
0x07f2a5f1a378cf71ab98a269d0b99b0e10e1e25309867fe915f07df906a78b53
WithdrawalsRoot:
0x45c3454331707a3784288564e4148b4952245d9d58daf6880a8e80e07afaabc8
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x4c90e53b28cedbe2d5fb6fdce8d060c1b14a5a353688e3931a5e5bfc7ef8cd68
Parent Root Hash:
0xdb1372983e68875d72327e4eebb16e51ac057da759afb7326d2b564e9e557eaf
Beacon Chain Deposit Count:
1666100
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xbed71e1e09828966bdbe5fd72c2036e1a4f80e93cadd0d0f9ec14d7a18e919e1
Randao Reveal:
0x83b3ca80cb577266f4dc4afc4b6f806d2cad9b8527f629884141969afb84cc9d622c6c2d20ff9d75ae8501c30db762e0038185c7a7f9d2f65847dc1532f43e2a90dba46848811e809bb79384733558409544ba4a3bbf8348e3fd76aff2c588fc
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.024368158937382458 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
256 KiB (2 blobs)
Blob Utilisation:
2 Blobs (33.33%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
262,144 (33.33%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000262144 ETH
Excess Blob Gas:
0 (0 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.