← previous blocknext block →recent activity
Analyzing
Block #87,610,607
11 transactions · 10 stateful · 2026-07-14 02:31:25 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
0.91
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,610,607 · 11 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
1w02w13w04w16w27w310w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x212c5b04…5f01
0x34b655…2a6f
6 touches
3 conflicts
0x640530ff…86bc
0x34b655…2a6f
6 touches
3 conflicts
0x745952b2…d90c
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xf2f40f08…5cdb
0x34b655…2a6f
6 touches
3 conflicts
0x6516c365…2dd2
0x34b655…2a6f
4 touches
1 conflict
0x6aa1497c…2292
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity