← previous blocknext block →recent activity
Analyzing
Block #86,916,341
19 transactions · 17 stateful · 2026-07-10 21:08:38 UTC
Parallelism
84/100
Blocked
24%
Avg conflicts / tx
0.32
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,916,341 · 19 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
4w05w16w17w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ae9d2df…f787
0x34b655…2a6f
6 touches
3 conflicts
0xbb277c58…e388
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0ae9d2df…f788
0x34b655…2a6f
6 touches
3 conflicts
0x0db25069…2fd1
0x34b655…2a6f
4 touches
1 conflict
0x21683d77…4e07
0x34b655…2a6f
4 touches
1 conflict
0x2b99c444…1332
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x0ae9d2df9c…16f787
Audit this contract →
← previous block·next block →recent activity