← previous blocknext block →recent activity
Analyzing
Block #87,713,558
16 transactions · 14 stateful · 2026-07-14 13:59:49 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,713,558 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w06w19w210w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa629d950…36f6
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x426e1f22…5ff9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4c243374…55e2
0x34b655…2a6f
4 touches
1 conflict
0x8f7038d3…3804
0x34b655…2a6f
4 touches
1 conflict
0x909b34ee…b9e3
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 0xa629d950d8…d936f6
Audit this contract →
← previous block·next block →recent activity