← previous blocknext block →recent activity
Analyzing
Block #86,833,709
20 transactions · 16 stateful · 2026-07-10 11:56:11 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,833,709 · 20 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
1w02w13w28w09w110w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x55642f63…03d6
0x34b655…2a6f
4 touches
1 conflict
0x258a1bba…3977
0x40c49f…2af0
2 touches
0 conflicts
0x27c47be6…d8f2
0x40c49f…2af0
2 touches
0 conflicts
0x79bf361d…06ab
0x40c49f…2af0
2 touches
0 conflicts
0x8dc9b9d5…6673
0x40c49f…2af0
2 touches
0 conflicts
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity