← previous blocknext block →recent activity
Analyzing
Block #94,952,185
18 transactions · 16 stateful · 2026-08-11 03:18:29 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,952,185 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w18w110w211w312w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8bc53a3…c2fe
0x34b655…2a6f
6 touches
3 conflicts
0x45ea7a97…bbb3
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x2471ab9e…4d43
0x34b655…2a6f
4 touches
1 conflict
0x2794fd34…c82f
0x34b655…2a6f
4 touches
1 conflict
0x48260180…a411
0x34b655…2a6f
4 touches
1 conflict
0x48260180…a412
0x34b655…2a6f
4 touches
1 conflict
0x76c4d722…afa9
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0xd8bc53a346…42c2fe
Audit this contract →
← previous block·next block →recent activity