← previous blocknext block →recent activity
Analyzing
Block #86,619,211
25 transactions · 23 stateful · 2026-07-09 12:02:05 UTC
Parallelism
72/100
Blocked
48%
Avg conflicts / tx
0.96
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,619,211 · 25 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
1w02w16w07w18w29w310w411w517w118w422w123w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1a8
0xb1dbf0…c0d3
10 touches
10 conflicts
0x8a35acfb…d1a9
0xb1dbf0…c0d3
10 touches
10 conflicts
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0335ae80…8414
0xb1dbf0…c0d3
4 touches
1 conflict
0x143dba04…1b98
0xb1dbf0…c0d3
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity