← previous blocknext block →recent activity
Analyzing
Block #87,625,310
10 transactions · 7 stateful · 2026-07-14 04:09:43 UTC
Parallelism
70/100
Blocked
29%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,625,310 · 10 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
1w03w04w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd337aaf…cb5e
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x08330b36…ae29
0x34b655…2a6f
4 touches
1 conflict
0x2cfa1fc4…f66b
0x34b655…2a6f
4 touches
1 conflict
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0x62cc9214…441b
0x34b655…2a6f
4 touches
1 conflict
0x6aea3f64…bb1f
0x34b655…2a6f
4 touches
1 conflict
0x6e23aa69…8dbb
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 0xbd337aafc4…bccb5e
Audit this contract →
← previous block·next block →recent activity