← previous blocknext block →recent activity
Analyzing
Block #87,586,913
16 transactions · 13 stateful · 2026-07-13 23:52:57 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,586,913 · 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
1w02w18w09w111w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x15bb0662…b802
0x34b655…2a6f
4 touches
1 conflict
0x199944d5…ab9f
0x34b655…2a6f
4 touches
1 conflict
0x1fd3f0d8…516d
0x34b655…2a6f
4 touches
1 conflict
0x2848aeee…60ee
0x34b655…2a6f
4 touches
1 conflict
0x3957d03b…147c
0x34b655…2a6f
4 touches
1 conflict
0x64312ffa…cdfa
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity