← previous blocknext block →recent activity
Analyzing
Block #86,689,726
24 transactions · 18 stateful · 2026-07-09 19:54:14 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,689,726 · 24 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
1w04w05w16w28w210w112w313w414w515w622w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x53c922c1…1f78
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x3053f66c…3a23
0x34b655…2a6f
4 touches
1 conflict
0x59b0a8da…0928
0x34b655…2a6f
4 touches
1 conflict
0x6083af24…a0df
0x34b655…2a6f
4 touches
1 conflict
0x70ff9262…8d80
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
15 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity