← previous blocknext block →recent activity
Analyzing
Block #86,663,688
22 transactions · 18 stateful · 2026-07-09 17:00:26 UTC
Parallelism
73/100
Blocked
44%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,663,688 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w18w29w315w416w520w221w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x342f88f5…2a06
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x77aa49e7…df90
0x34b655…2a6f
4 touches
1 conflict
0x793d86d7…acc4
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8b87ece6…3353
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
6 conflicts on slot 0x342f88f552…882a06
Audit this contract →
← previous block·next block →recent activity