Block
#0xb57140899cb9d2718a5f156b03d7e0e2072d9ad257843fb8ba8bbc776215d0f3
Status:
Finalized
Timestamp:
374 days ago (Jul-10-2023 12:10:47 PM +UTC)
Transactions:
110 transactions and 62 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
MEV Builder: 0x333...203 in 12 secs
Block Reward:
0.053300962931078304 ETH (0 + 0.261193566151506408 - 0.207892603220428104)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
63,631 bytes
Gas Used:
12,282,028 (40.94%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000016926569718 ETH (16.926569718 Gwei)
Burnt Fees:
š„ 0.207892603220428104 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$1,880.69 / ETH
Hash:
0xb57140899cb9d2718a5f156b03d7e0e2072d9ad257843fb8ba8bbc776215d0f3
StateRoot:
0x2a43a9563fc95fae9f312907dcc1af9ae3bc9acd5de71d8462caf0a7a0bd58ef
WithdrawalsRoot:
0x5ba3aad142c17ef8aa921e3d9dda25779a7895e58a966d9823239deac3b5e372
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x20cd854cc4cdbdd5774e7ac82ef4fefacc7db10c0cd25c19d6c4234b14f44b32
Parent Root Hash:
0x2c73f3c369bf553bdc94ef64d11491a92bbadcd4780bdbfe192eedbe6188b29a
Beacon Chain Deposit Count:
845617
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xe0b532374ed208ee4c14121999556b1ab8059bdab40cddfd9a0c2c7367f7fa63
Randao Reveal:
0xabc0178a1ebf152c7a2e3b3e3c88d2d16bf7f85fec102708d61e382e0c48a3ef0f4494a4389ca935b6646865e8c0d91f18fadd9828f58e687a918b879de4e5043b44d699becd598b8e6ee5ad088e84db8b73169ae9274c363d1d00c9c20f429f
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.053326699548043606 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
Blob Utilisation:
Blob Gas Price:
Blob Gas Used:
Blob Gas Limit:
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.