← previous blocknext block →recent activity
Analyzing
Block #87,717,734
18 transactions · 17 stateful · 2026-07-14 14:27:56 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,717,734 · 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
1w02w13w04w15w06w110w211w315w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a1604d1…3e8a
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x5e0b8bbe…377b
0x34b655…2a6f
6 touches
3 conflicts
0x7584bc06…3463
0x34b655…2a6f
6 touches
3 conflicts
0x13510de3…1c68
0x34b655…2a6f
4 touches
1 conflict
0x2003d8cf…6836
0x34b655…2a6f
4 touches
1 conflict
0x293fed86…ed95
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
6 conflicts on slot 0x6a1604d1a5…053e8a
Audit this contract →
← previous block·next block →recent activity