← previous blocknext block →recent activity
Analyzing
Block #86,925,068
14 transactions · 14 stateful · 2026-07-10 22:06:59 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,925,068 · 14 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
1w02w16w07w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd526b516…a51a
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x64852187…6cb0
0x34b655…2a6f
6 touches
3 conflicts
0x64852187…6caf
0x34b655…2a6f
6 touches
3 conflicts
0x0df3c660…1cbe
0x34b655…2a6f
4 touches
2 conflicts
0x5a310d83…cae0
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0xd526b51665…59a51a
Audit this contract →
← previous block·next block →recent activity