← previous blocknext block →recent activity
Analyzing
Block #86,660,225
40 transactions · 35 stateful · 2026-07-09 16:37:21 UTC
Parallelism
63/100
Blocked
71%
Avg conflicts / tx
3.73
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #86,660,225 · 40 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w37w411w012w113w214w315w416w517w618w719w820w921w1022w1123w1224w1325w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
30 touches
105 conflicts
0xc368d7fd…aaec
0x34b655…2a6f
12 touches
15 conflicts
0xd786a4f1…12d6
0x34b655…2a6f
12 touches
15 conflicts
0x3a2a8323…3f40
0x34b655…2a6f
12 touches
15 conflicts
0x485ae99d…f26f
0x34b655…2a6f
12 touches
15 conflicts
0xe6805ef8…e22e
0x34b655…2a6f
12 touches
15 conflicts
0x727fbce7…0c80
0x34b655…2a6f
12 touches
15 conflicts
0x8388eab6…83ff
0x34b655…2a6f
12 touches
15 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
105 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity