← previous blocknext block →recent activity
Analyzing
Block #92,200,536
20 transactions · 17 stateful · 2026-08-01 12:19:29 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,200,536 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w19w212w213w317w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81561f70…fefd
0x34b655…2a6f
6 touches
3 conflicts
0x0533644f…aefa
0x34b655…2a6f
4 touches
1 conflict
0x0b65d0ba…a344
0x34b655…2a6f
4 touches
1 conflict
0x0b65d0ba…a345
0x34b655…2a6f
4 touches
1 conflict
0x0ea06e29…aa72
0x34b655…2a6f
4 touches
1 conflict
0x2385516f…eca5
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x38a88cf1…ec2d
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 0x81561f70ba…26fefd
Audit this contract →
← previous block·next block →recent activity