← previous blocknext block →recent activity
Analyzing
Block #86,678,676
30 transactions · 27 stateful · 2026-07-09 18:40:27 UTC
Parallelism
63/100
Blocked
59%
Avg conflicts / tx
1.47
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #86,678,676 · 30 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w07w18w29w310w411w512w616w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x459573ed…fbbe
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x65338476…2209
0x34b655…2a6f
8 touches
6 conflicts
0xb46ee126…a1a5
0x34b655…2a6f
6 touches
3 conflicts
0xbc7b467b…1fef
0x34b655…2a6f
6 touches
3 conflicts
0xe3321cb6…26de
0x34b655…2a6f
6 touches
3 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
6 touches
3 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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity