← previous blocknext block →recent activity
Analyzing
Block #87,682,861
20 transactions · 20 stateful · 2026-07-14 10:34:19 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,682,861 · 20 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
1w02w13w04w15w06w110w112w214w217w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b8532b7…d8f9
0x34b655…2a6f
6 touches
3 conflicts
0xa10e928f…3b92
0x34b655…2a6f
6 touches
3 conflicts
0x745952b2…d90c
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4a3
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4b2
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 0x4b8532b71d…fed8f9
Audit this contract →
← previous block·next block →recent activity