← previous blocknext block →recent activity
Analyzing
Block #87,121,403
11 transactions · 11 stateful · 2026-07-11 19:58:34 UTC
Parallelism
55/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,121,403 · 11 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
2w03w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x4c7b72e8…9a1f
0x34b655…2a6f
6 touches
3 conflicts
0xbac9c9a2…b708
0x34b655…2a6f
6 touches
3 conflicts
0x1e166a45…98a7
0x34b655…2a6f
4 touches
1 conflict
0x212c3c82…4f2a
0x34b655…2a6f
4 touches
1 conflict
0x32239aa3…2aac
0x34b655…2a6f
4 touches
1 conflict
0x36aa3d34…91c7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity