← previous blocknext block →recent activity
Analyzing
Block #86,926,604
11 transactions · 11 stateful · 2026-07-10 22:17:15 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,926,604 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w29w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba559de1…6d2c
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x3b787279…727f
0x34b655…2a6f
4 touches
1 conflict
0x494d61cd…c1cd
0x34b655…2a6f
4 touches
1 conflict
0x5571e830…9cea
0x34b655…2a6f
4 touches
1 conflict
0x57330c5d…9973
0x34b655…2a6f
4 touches
1 conflict
0x6d42d870…6630
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
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 0xba559de17c…336d2c
Audit this contract →
← previous block·next block →recent activity