← previous blocknext block →recent activity
Analyzing
Block #87,065,927
17 transactions · 16 stateful · 2026-07-11 13:48:04 UTC
Parallelism
59/100
Blocked
44%
Avg conflicts / tx
0.94
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,065,927 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w19w210w311w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x1b374c44…96d9
0x34b655…2a6f
8 touches
6 conflicts
0xc5e55770…12e8
0x34b655…2a6f
6 touches
3 conflicts
0xc5e55770…12e9
0x34b655…2a6f
6 touches
3 conflicts
0x230a3fb0…e64c
0x34b655…2a6f
6 touches
3 conflicts
0xb4ab4257…11d7
0x34b655…2a6f
6 touches
3 conflicts
0xafd867b7…2b2d
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity