Block
#20038366
Status:
Finalized
Timestamp:
165 days ago (Jun-07-2024 07:10:11 AM +UTC)
Transactions:
179 transactions and 95 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.052320366446667258 ETH (0 + 0.256801240261751642 - 0.204480873815084384)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
66,259 bytes
Gas Used:
16,061,168 (53.54%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000012731382538 ETH (12.731382538 Gwei)
Burnt Fees:
š„ 0.204480873815084384 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,676.79 / ETH
Hash:
0x27c31d2946b19732013fc6f13aa74ff61198f1a0e259e3f4e2ba7e6d3bc3801d
StateRoot:
0xc18ea5c77aea6f623ab7acbecf84580446f3984c614077b80a9fc18316662f29
WithdrawalsRoot:
0x29b29ac4e779d7e7b83eb476cceb43412388b7fcc6af28db5d76bf0b9a027679
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x77b21d0f5fcee59bc189f8d1804212fd471761580d8dab29c4ccac3cf00a0b2c
Parent Root Hash:
0x55060a4c6e9a03a362661b9711e622e849d06daec460a720c423a63ffe056974
Beacon Chain Deposit Count:
1519845
Slot Graffiti:
FSKCR (Hex:0x46534b4352000000000000000000000000000000000000000000000000000000)
Block Randomness:
0xa6657dc920f10fe3f83ab8a366b82668eb157629cef5084e7df2430e6e12e49c
Randao Reveal:
0xae93d8bfd24e4a345c10a9c7ddfcff3a33a93aa984aca346a602dfd1e16669a9caf1b07caf7676140eff4a222ca5371007feeb414e23aeb2292711968ba941a3c7fc462181144a590427f45c206e0b600e0dcf26115996626c9af416f87b44bd
Proposer Fee Recipient:
0x572F27cF5Bd03719D9588964C907a908877894AE (Fee Recipient: 0x572...4AE)
MEV Reward:
0.063219253952318864 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
512 KiB (4 blobs)
Blob Utilisation:
4.00 Blobs (66.67%)
Blob Gas Price:
7 wei (0.000000007 Gwei)
Blob Gas Used:
524,288 (66.67%)
Blob Gas Limit:
786,432
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.