← previous blocknext block →recent activity
Analyzing
Block #93,466,811
16 transactions · 14 stateful · 2026-08-05 22:30:44 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,466,811 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w09w010w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x729c91b8…9537
0x188d58…ea8e
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Wrapped Ether (WETH)
1 conflict on slot 0x56a919c43e…27ab49
Audit this contract →
← previous block·next block →recent activity