← previous blocknext block →recent activity
Analyzing
Block #87,132,222
21 transactions · 20 stateful · 2026-07-11 21:10:50 UTC
Parallelism
76/100
Blocked
25%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,132,222 · 21 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
6w07w111w212w314w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8b818135…eff8
0x34b655…2a6f
6 touches
3 conflicts
0x220a8541…6431
0x34b655…2a6f
4 touches
1 conflict
0x4c7b72e8…9a1f
0x34b655…2a6f
4 touches
1 conflict
0x648911a3…2958
0x34b655…2a6f
4 touches
1 conflict
0x6571f9fa…3b7c
0x34b655…2a6f
4 touches
1 conflict
0x72470f81…c402
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity