← previous blocknext block →recent activity
Analyzing
Block #87,902,706
15 transactions · 15 stateful · 2026-07-15 11:05:13 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,902,706 · 15 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
1w02w13w24w05w17w08w111w212w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9f83113a…dcd8
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x3347cbe5…846c
0x34b655…2a6f
4 touches
1 conflict
0x5de95e2f…4c8f
0x34b655…2a6f
4 touches
1 conflict
0x6095a759…fc32
0x34b655…2a6f
4 touches
1 conflict
0x65e795ca…0320
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 0x9f83113ae0…0edcd8
Audit this contract →
← previous block·next block →recent activity