← previous blocknext block →recent activity
Analyzing
Block #86,707,086
22 transactions · 18 stateful · 2026-07-09 21:50:01 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
0.77
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,707,086 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w316w417w518w619w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc3f7ee8…7924
0x34b655…2a6f
8 touches
11 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
8 touches
6 conflicts
0x511ecf07…8ed0
0x34b655…2a6f
6 touches
3 conflicts
0x548145a9…cfce
0x34b655…2a6f
6 touches
3 conflicts
0x60c7217a…8c94
0x34b655…2a6f
6 touches
3 conflicts
0x63b15849…80b2
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0xb1c67a7d…b9b1
0x34b655…2a6f
6 touches
3 conflicts
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
11 conflicts on slot 0xcc3f7ee8e4…307924
Audit this contract →
← previous block·next block →recent activity