← previous blocknext block →recent activity
Analyzing
Block #87,060,833
15 transactions · 13 stateful · 2026-07-11 13:14:04 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,060,833 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w310w411w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xddbe18ed…2158
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x88fb89dd…f591
0x34b655…2a6f
6 touches
3 conflicts
0x52afad34…6c7c
0x34b655…2a6f
6 touches
3 conflicts
0x676d5418…85ea
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x81e1b637…2b3b
0x34b655…2a6f
6 touches
3 conflicts
0xe087db9c…7d87
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xddbe18ed88…cd2158
Audit this contract →
← previous block·next block →recent activity