← previous blocknext block →recent activity
Analyzing
Block #87,736,073
18 transactions · 16 stateful · 2026-07-14 16:30:36 UTC
Parallelism
78/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,736,073 · 18 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
2w05w16w212w315w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb65644e3…33ce
0x34b655…2a6f
6 touches
3 conflicts
0x307414a5…7214
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x11d928aa…33a4
0x34b655…2a6f
4 touches
1 conflict
0x5c591136…d322
0x34b655…2a6f
4 touches
1 conflict
0x5f669600…d225
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 0xb65644e3fe…5033ce
Audit this contract →
← previous block·next block →recent activity