Block
#17869635
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
945 days ago (Aug-08-2023 10:33:47 AM +UTC)
Transactions:
116 transactions and 68 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
builder0x69 in 12 secs
Block Reward:
0.069963519487179692 ETH (0 + 0.333006018521251889 - 0.263042499034072197)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
49,964 bytes
Gas Used:
12,161,267 (40.54%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000021629530791 ETH (21.629530791 Gwei)
Burnt Fees:
🔥 0.263042499034072197 ETH
Extra Data:
builder0x69 (Hex:0x6275696c64657230783639)
Ether Price:
$1,855.73 / ETH
Hash:
0xb4f11c13e8a1c543f695096df76585c4e27fa8dfac50e0213e5fed279d84ee9b
StateRoot:
0xfef48c5533f7404369a1e6e27a6ea3defe34fd1caededcdecdf6e71a57606333
WithdrawalsRoot:
0xb2c1013ad9f665d9868e6c53e4eceffedb3399476ae2128ddac764059e3ae448
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xd86afee83a2ac46eb2d5298924a365f0edf273652e2f2b4c65c8626548bfd6b7
Parent Root Hash:
0x9aefaf7594b59f699aad5c5ee35bc5b04ebdeab6df0594f80b75c3df5b52c3f2
Beacon Chain Deposit Count:
898464
Slot Graffiti:
poapqFgrWg9hW8Idd4BhhVcEK+YLMu0A (Hex:0x706f617071466772576739685738496464344268685663454b2b594c4d753041)
Block Randomness:
0x15a91e8df5d984e48d0cb893de84f5cce8bfae9eed176e87cc060c36c7ebf0ae
Randao Reveal:
0x8966ddc19c7d1a5f09d71a1a6b11ea383cf0d8cd81d1fe8cd3f29a5c6f598ce21f6e65b086ca02e85fafb88890986f72085c865f3aa210bba7b51004c76ff1be3da228530cbfa5e9374a4501829cc0563aa6357d98782f33db9e93c4417550a2
Proposer Fee Recipient:
0x9f4B4CeCa7aCE96834Bd2fcC961c772De7cb481a (Fee Recipient: 0x9f...81a)
MEV Reward:
0.092790475277271831 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.