← previous blocknext block →recent activity
Analyzing
Block #87,722,216
18 transactions · 17 stateful · 2026-07-14 14:57:55 UTC
Parallelism
78/100
Blocked
24%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,722,216 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w19w210w311w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x70d66bd9…0ffa
0x34b655…2a6f
6 touches
3 conflicts
0xe1c784c4…ac83
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x426e1f22…5ff9
0x34b655…2a6f
4 touches
1 conflict
0x201ddf34…6e07
0x34b655…2a6f
4 touches
1 conflict
0x201ddf34…6e08
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
6 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity