← previous blocknext block →recent activity
Analyzing
Block #86,905,630
23 transactions · 21 stateful · 2026-07-10 19:57:05 UTC
Parallelism
74/100
Blocked
62%
Avg conflicts / tx
1.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,905,630 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w27w08w19w210w311w012w113w214w315w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
12 touches
15 conflicts
0x8dfef5ae…9361
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xb372efbe…1085
0xd32edf…ff58
7 touches
6 conflicts
0x7da56943…9753
0x34b655…2a6f
6 touches
3 conflicts
0x178457f9…d26a
0x34b655…2a6f
6 touches
3 conflicts
0x6b7a5994…47ef
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
15 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity