← previous blocknext block →recent activity
Analyzing
Block #86,790,292
21 transactions · 19 stateful · 2026-07-10 07:05:48 UTC
Parallelism
62/100
Blocked
68%
Avg conflicts / tx
2.05
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,790,292 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w37w48w59w010w011w112w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63c900f4…2600
0x34b655…2a6f
14 touches
21 conflicts
0x922c7ebd…6600
0xc8689a…ee79
14 touches
21 conflicts
0x727fbce7…0c80
0x34b655…2a6f
14 touches
21 conflicts
0x96047c45…b64a
0x34b655…2a6f
12 touches
15 conflicts
0xe7488796…72d7
0xd32edf…ff58
11 touches
15 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
10 touches
10 conflicts
0xc368d7fd…aaec
0x34b655…2a6f
10 touches
10 conflicts
0x79d50d4a…951d
0x34b655…2a6f
8 touches
6 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 0x63c900f479…962600
Audit this contract →
← previous block·next block →recent activity