← previous blocknext block →recent activity
Analyzing
Block #87,489,458
21 transactions · 20 stateful · 2026-07-13 13:00:21 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,489,458 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w07w212w114w315w417w520w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96bfa04d…d06b
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x88adad52…54b7
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xf1cc9519…84c1
0x34b655…2a6f
6 touches
3 conflicts
0x4c04ce68…d007
0x34b655…2a6f
4 touches
1 conflict
0x82437f64…3f11
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 0x96bfa04d52…3ed06b
Audit this contract →
← previous block·next block →recent activity