← previous blocknext block →recent activity
Analyzing
Block #86,920,683
25 transactions · 17 stateful · 2026-07-10 21:37:37 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,920,683 · 25 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
1w08w19w012w013w115w216w319w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0xc1add9b2…ad0b
0x34b655…2a6f
6 touches
3 conflicts
0x1dddd7ef…8f05
0x34b655…2a6f
6 touches
3 conflicts
0x98460be4…2ef8
0x34b655…2a6f
6 touches
3 conflicts
0x0d2e1791…c1dd
0x34b655…2a6f
4 touches
1 conflict
0x12573732…e891
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x45cd8987…3132
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
10 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity