← previous blocknext block →recent activity
Analyzing
Block #85,933,194
20 transactions · 18 stateful · 2026-07-06 07:38:36 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,933,194 · 20 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
1w02w15w06w110w212w013w114w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62341e2a…2d78
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x427c9fc4…5cee
0x34b655…2a6f
6 touches
3 conflicts
0x35a9f06c…7689
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x213a54fa…c85f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x33e3dcdd…1f1f
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 0x62341e2aa6…ba2d78
Audit this contract →
← previous block·next block →recent activity