← previous blocknext block →recent activity
Analyzing
Block #86,621,082
21 transactions · 18 stateful · 2026-07-09 12:14:32 UTC
Parallelism
52/100
Blocked
61%
Avg conflicts / tx
2.05
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,621,082 · 21 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w69w713w718w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98d58911…19f2
0x34b655…2a6f
16 touches
28 conflicts
0x922c7ebd…6600
0xc8689a…ee79
14 touches
21 conflicts
0x63c900f4…2600
0x34b655…2a6f
14 touches
21 conflicts
0x727fbce7…0c80
0x34b655…2a6f
14 touches
21 conflicts
0xed660153…a905
0x34b655…2a6f
14 touches
21 conflicts
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0x22bc4ea4…5c8a
0x34b655…2a6f
10 touches
10 conflicts
0x6b2ba712…0214
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0x98d589117f…0c19f2
Audit this contract →
← previous block·next block →recent activity