Block
#19816730
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
664 days ago (May-07-2024 07:34:59 AM +UTC)
Transactions:
201 transactions and 47 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.047433567390230826 ETH (0 + 0.145273146791321064 - 0.097839579401090238)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
58,831 bytes
Gas Used:
14,469,374 (48.23%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000006761839137 ETH (6.761839137 Gwei)
Burnt Fees:
🔥 0.097839579401090238 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,005.91 / ETH
Hash:
0x79f033282fcd6d8f50f3e567462db7e6ddbc132ed596194b785b3ac27a95c925
StateRoot:
0x1cb952ed3ad0288fee155c6bd9db45d44b52f8ccf9452f431de07d8102e20f6c
WithdrawalsRoot:
0x79ad9f5f4c43bf426c4589ff345bc55c0cbd295facbb378239fdd1133b2fb96b
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x5cbd8eacaa16fbad7539efc77f137b2afad722d3e49ecd0b91a2af1e6b247e22
Parent Root Hash:
0x7e4b71896e11f53288245c10109a118f29eebfb320776f7bc681116db39c59ed
Beacon Chain Deposit Count:
1465115
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xb9696fb53ef54a4abe85661fa697badd38f66129f001d06fdff3d9b2e19655ce
Randao Reveal:
0xa535b7e9f1d1337477a660f5bfb54297ce205681211c939b839fcfbd26c6c540a2b1201e96647c58b3f57f1e19d50ff605bcbec08165fb1c281d64529dfbc4f2685047be405aa8bf24398ba3843b0ce6c219c2ee29e7936b548464f127d9b63e
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.050540335845665561 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
384 KiB (3 blobs)
Blob Utilisation:
3 Blobs (50.00%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
393,216 (50.00%)
Blob Gas Limit:
786,432
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.