← previous blocknext block →recent activity
Analyzing
Block #85,191,149
19 transactions · 19 stateful · 2026-07-02 21:15:30 UTC
Parallelism
74/100
Blocked
32%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,191,149 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w16w27w316w117w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdd7f0a5…d417
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x1bfc029c…f91e
0x34b655…2a6f
6 touches
3 conflicts
0x7dbd84bc…b2a6
0x34b655…2a6f
6 touches
3 conflicts
0x8cb73ef2…16e3
0x34b655…2a6f
6 touches
3 conflicts
0x8e507257…71c1
0x34b655…2a6f
6 touches
3 conflicts
0x9ce1b493…4ee7
0x34b655…2a6f
6 touches
3 conflicts
0xa1571d54…ae41
0x34b655…2a6f
6 touches
3 conflicts
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
6 conflicts on slot 0xcdd7f0a502…4ed417
Audit this contract →
← previous block·next block →recent activity