← previous blocknext block →recent activity
Analyzing
Block #86,933,342
21 transactions · 16 stateful · 2026-07-10 23:02:15 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,933,342 · 21 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
5w06w09w110w211w212w318w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xaedc3dd6…3c3b
0x34b655…2a6f
6 touches
3 conflicts
0x3ba014e3…35d5
0x34b655…2a6f
6 touches
3 conflicts
0x9068a9bc…86ee
0x34b655…2a6f
4 touches
1 conflict
0x92132ed7…2722
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity