← previous blocknext block →recent activity
Analyzing
Block #87,329,191
13 transactions · 11 stateful · 2026-07-12 19:08:36 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,329,191 · 13 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
5w07w18w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xd7320039…3bc0
0x34b655…2a6f
4 touches
1 conflict
0xf5c132ea…e166
0x34b655…2a6f
4 touches
1 conflict
0x1d84bebc…07d0
0x34b655…2a6f
4 touches
1 conflict
0x1d84bebc…07d1
0x34b655…2a6f
4 touches
1 conflict
0x288961aa…ac7f
0x34b655…2a6f
4 touches
1 conflict
0x2e4e7336…e906
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity