← previous blocknext block →recent activity
Analyzing
Block #87,595,662
18 transactions · 14 stateful · 2026-07-14 00:51:29 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,595,662 · 18 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
3w04w15w28w09w110w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x11c40774…adbe
0x34b655…2a6f
6 touches
3 conflicts
0x12a92ce8…db54
0x34b655…2a6f
6 touches
3 conflicts
0x176771f9…c1a4
0x34b655…2a6f
6 touches
3 conflicts
0x2a5bc5cd…0a17
0x34b655…2a6f
6 touches
3 conflicts
0x2a88784d…f1be
0x34b655…2a6f
6 touches
3 conflicts
0x2b5101ac…090b
0x34b655…2a6f
6 touches
3 conflicts
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity