ETH Price: $2,006.03 (-3.87%)

Block

#17732013
Block Height:
17732013
Status:
Finalized
Timestamp:
941 days ago (Jul-20-2023 04:31:35 AM +UTC)
Proposed On:
Block proposed on slot 6916956 , epoch 216154
Transactions:
Withdrawals:
16 withdrawals in this block

Fee Recipient:
Block Reward:
0.056071578984619722 ETH (0 + 0.2431053363276906 - 0.187033757343070878)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
47,250 bytes

Gas Used:
10,019,946 (33.40%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000018666144243 ETH (18.666144243 Gwei)
Burnt Fees:
🔥 0.187033757343070878 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$1,891.68 / ETH
Hash:
0x2e134b50bec7a64f792206bec287e4cdccb6c67e0a625df8bfb4dd0d1b247382
StateRoot:
0xde684f92ac22003b9900730b0515080336c104bd61b4b371513fee30df6a3807
WithdrawalsRoot:
0x2705f4355769a44c49282614884107ec92e56e8edc075745c3da1214207e75af
Nonce:
0x0000000000000000

Slot:
Epoch:
Proposer Index:

Slot Root Hash:
0x997ec3b3579df760c16d54c0544a6ee532bac13cccd23a79cd6da3d652922df2
Parent Root Hash:
0x6a643de04e8f7e365c94d358cba81d47f965bfb04f0770a3bcff6849e1830b6c
Beacon Chain Deposit Count:
866647
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x1aa926167a0aa2301f8ed0d3f1d30bbcff76b4abd4986ab4b79e62312b7a08d4
Randao Reveal:
0x84a355f1c1d655ab3f91e0e9c439a8cd98307f4667e863971e66aa69bb6d6349d81f4d6fca9318b4b3da426a6665097e1095e76aaeab2f63ad529696aedba5cc58694b9bd46c4cfceabdd910fa65e1cb162e227dd5d16392a77e9e5b0730e85c
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.055658851869262749 ETH
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.