Block
#20238588
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
599 days ago (Jul-05-2024 06:43:11 AM +UTC)
Transactions:
491 transactions and 97 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.066800103264145516 ETH (0 + 0.389868590180601672 - 0.323068486916456156)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
250,570 bytes
Gas Used:
27,461,548 (91.54%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000011764394597 ETH (11.764394597 Gwei)
Burnt Fees:
š„ 0.323068486916456156 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$2,982.07 / ETH
Hash:
0xa1300a632e127bcd7fa57bc5d4e6dcb1fb8b6682de38f018e0707510073ac96d
StateRoot:
0x5aa7d73dcf0920a771315591f2274d5f625d4100cdaeadc3eb713468d126dc86
WithdrawalsRoot:
0xeb37e09a012d6c3fb125544119ff78359e67847746e2d00e2e07b52cb918733d
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xb605f5a7f9bb6d6ad354e1c4e9350287aa7eba6ac855e4c54444e57922a46d85
Parent Root Hash:
0x39d647c63ed68297a3b31b918a906b7385f1d02d81fce919c03d178b659f6080
Beacon Chain Deposit Count:
1571663
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xb1bf55c8e59e9939c63c349280c816aab9a12d454acdf7ad5b02e8a42f731709
Randao Reveal:
0xa6464794e2e3196ed4e5cc784fff951a44668cfbb83b348e7f45169dfa65717d1b84c04913ad78e2b75636289fe3bb6817e826f05c893ad9aaccef0ec696535c7157509a3b698aea8f2f6741cf88ffbf93496ddd42c60bbace986d64f6c1d3b4
Proposer Fee Recipient:
0xcDA9D71bdfAe59b89Cee131eD3079f8AC4c77062 (MEV Builder: 0xcDA...062)
MEV Reward:
0.108453371200406233 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6 Blobs (100.00%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
786,432 (100.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000786432 ETH
Excess Blob Gas:
524,288 (4 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.