Block
#20363733
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
581 days ago (Jul-22-2024 06:02:59 PM +UTC)
Transactions:
283 transactions and 130 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.049145965111674586 ETH (0 + 0.171324914846928102 - 0.122178949735253516)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
123,703 bytes
Gas Used:
29,989,042 (99.96%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000004074119798 ETH (4.074119798 Gwei)
Burnt Fees:
š„ 0.122178949735253516 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,441.05 / ETH
Hash:
0xafbb072079770762229d218394907336cbae3fe32c480e13775ac27cfb2bd25d
StateRoot:
0x53c5bd1a7f4e661f1846f40f6ee06d8cd8b3a528fea3e58d7c274ec52055f16a
WithdrawalsRoot:
0x04910c0415bb277df7e51d10ae267abe4bf0d0fca727dc2046ebd678bffca9e5
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xf0b7c3f41f340ef7319e84dc15086fa9a0b1f0ddea08bf414847931e7522e280
Parent Root Hash:
0xa095e9ca5b2b8e702ae0e27b2d4d46739a1c66a03344af7448e1e77979564823
Beacon Chain Deposit Count:
1602503
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x328a6a668ff72bcc4711219644245ff01c0c77f978e43a42ecf8d000b790ad28
Randao Reveal:
0x93b6e4f743edcaa0f8576e8bf2d30735dfb131511c12d8d910ce5853bba640cb7d41c50d7acfa03ab44d9e40c1087499121ac40ead67fb3259e3d8025a0abcd003e0faab525c8f75e551a2da486ddec48159d7cf0eb34908929ede51c42c4344
Proposer Fee Recipient:
0xE94f1fa4F27D9d288FFeA234bB62E1fBC086CA0c (Fee Recipient: 0xE94...A0c)
MEV Reward:
0.239240541016205169 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
512 KiB (4 blobs)
Blob Utilisation:
4 Blobs (66.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
524,288 (66.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000524288 ETH
Excess Blob Gas:
393,216 (3 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.