← previous blocknext block →recent activity
Analyzing
Block #87,791,665
17 transactions · 17 stateful · 2026-07-14 22:42:30 UTC
Parallelism
76/100
Blocked
35%
Avg conflicts / tx
0.94
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,791,665 · 17 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
2w03w15w06w07w210w111w212w315w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80656e3b…9240
0x34b655…2a6f
8 touches
6 conflicts
0xb44d5376…33cc
0x34b655…2a6f
8 touches
6 conflicts
0x2d7ea048…d78e
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xe1b723f0…7d5f
0x34b655…2a6f
6 touches
3 conflicts
0xea2644f5…8c97
0x34b655…2a6f
6 touches
3 conflicts
0x335892bb…ae71
0x34b655…2a6f
4 touches
1 conflict
0x3817bbca…1a2e
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 0x80656e3b9f…e39240
Audit this contract →
← previous block·next block →recent activity