Block
#23145601
Status:
Finalized
Timestamp:
226 days ago ()
Transactions:
187 transactions and 68 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.009560863722143318 ETH (0 + 0.016694066133007998 - 0.00713320241086468)
Total Difficulty:
0
Size:
82,267 bytes
Gas Used:
14,146,540 (31.44%)
Gas Limit:
45,000,000
Base Fee Per Gas:
0.000000000504236542 ETH (0.504236542 Gwei)
Burnt Fees:
š„ 0.00713320241086468 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$4,443.12 / ETH
Hash:
0x29f1a1611bdc1a5167de49e67158571cdf0eddde5add8e1c35e3868b936e1f4f
StateRoot:
0xd4db1365397dce55fe69b9a5d93f26d7ff0ef21e777563b96a69ea89eb33238b
WithdrawalsRoot:
0x5d0ce7e7831eb1d18a150da039224ded7944100327846271520718b5957df113
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x704eb79fa6a58d26ba459b8cf00ec991b7cac0d38f816b5125e5f3a8a5dce2bb
Parent Root Hash:
0x24c9bb0f5d5843b12a09ff83cd5a081f57e27c298a76016471bc08f44a53bf60
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
validating_from_DAppNode (Hex:0x76616c69646174696e675f66726f6d5f444170704e6f64650000000000000000)
Block Randomness:
0xf538015e2bae3d566736b06c21ee6e3cb47ef9a67dd9cba9fea8cef4bcfa5b79
Randao Reveal:
0xa1e98f1c37704e916eca04de4727409d740772b436c68fb8c141c40ed1f93304eb72a44c2ac1820b27d758bb01085b791384496fa79e7787d40f88f8721fdf6ca5a8f4bce990ecec042060475ce4612dacce2a19a1f8bf1922162ae0b9987cdd
Proposer Fee Recipient:
0xa684e47A0906f320960FA0487aCe021535ad0E54 (Fee Recipient: 0xa68...E54)
MEV Reward:
0.009892230796520534 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
384 KiB (3 blobs)
Blob Utilisation:
3 Blobs (33.33%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
393,216 (33.33%)
Blob Gas Limit:
1,179,648
Total Blob Fees:
0.000000000000393216 ETH
Excess Blob Gas:
0 (0 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.