← previous blocknext block →recent activity
Analyzing
Block #86,987,571
9 transactions · 7 stateful · 2026-07-11 05:04:32 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,987,571 · 9 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
2w03w16w2
- 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
0x45877cba…0b50
0x34b655…2a6f
6 touches
3 conflicts
0x7d6e48e8…f2b5
0x34b655…2a6f
4 touches
1 conflict
0x0921c970…9f93
0x34b655…2a6f
2 touches
0 conflicts
0x119a0fbf…f47c
0x34b655…2a6f
2 touches
0 conflicts
0x2b7f9199…7127
0x34b655…2a6f
2 touches
0 conflicts
0x34bd7c00…43fd
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