← previous blocknext block →recent activity
Analyzing
Block #86,804,174
17 transactions · 14 stateful · 2026-07-10 08:38:34 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,804,174 · 17 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
1w02w06w07w18w29w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x8e1b6032…695c
0xd32edf…ff58
3 touches
1 conflict
0x1d826725…e975
0x34b655…2a6f
2 touches
0 conflicts
0x1d846e91…95c0
0x34b655…2a6f
2 touches
0 conflicts
0x55642f63…03d6
0x34b655…2a6f
2 touches
0 conflicts
0x58f65aa1…8f98
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity