← previous blocknext block →recent activity
Analyzing
Block #88,158,513
10 transactions · 9 stateful · 2026-07-16 15:36:26 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,158,513 · 10 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
4w05w16w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0dd3d3cd…7281
0x34b655…2a6f
6 touches
3 conflicts
0x0d7d817f…6eee
0x34b655…2a6f
6 touches
3 conflicts
0x23eeba48…cc51
0x34b655…2a6f
4 touches
1 conflict
0x310afe2c…83e1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x505b37d8…d3fc
0x34b655…2a6f
4 touches
1 conflict
0x52a2ba74…f2f6
0x34b655…2a6f
4 touches
1 conflict
0x52a2ba74…f2f7
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 0x0dd3d3cd18…c87281
Audit this contract →
← previous block·next block →recent activity