← previous blocknext block →recent activity
Analyzing
Block #86,951,337
18 transactions · 16 stateful · 2026-07-11 01:02:27 UTC
Parallelism
72/100
Blocked
31%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,951,337 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w19w212w013w314w115w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0edff147…13ed
0x34b655…2a6f
4 touches
1 conflict
0x0edff147…13ee
0x34b655…2a6f
4 touches
1 conflict
0x17fbe072…2ea6
0x34b655…2a6f
4 touches
1 conflict
0x2b95e778…d7d0
0x34b655…2a6f
4 touches
1 conflict
0x3800d0ea…6168
0x34b655…2a6f
4 touches
1 conflict
0x7e7de6d7…48be
0x34b655…2a6f
4 touches
1 conflict
0x977e7afc…bf14
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