← previous blocknext block →recent activity
Analyzing
Block #86,625,067
20 transactions · 16 stateful · 2026-07-09 12:41:07 UTC
Parallelism
85/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,625,067 · 20 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
3w04w15w27w08w110w011w112w213w017w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56f247e6…b599
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x22bc4ea4…5c8a
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x250c8181…eef2
0x34b655…2a6f
4 touches
1 conflict
0x485ae99d…f26f
0x34b655…2a6f
4 touches
1 conflict
0x4e460439…5ba2
0x34b655…2a6f
4 touches
1 conflict
0x6b2ba712…0214
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 0x56f247e69a…1db599
Audit this contract →
← previous block·next block →recent activity