← previous blocknext block →recent activity
Analyzing
Block #86,632,444
34 transactions · 27 stateful · 2026-07-09 13:30:28 UTC
Parallelism
68/100
Blocked
63%
Avg conflicts / tx
1.38
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #86,632,444 · 34 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
1w03w18w09w010w111w212w313w414w519w121w623w626w128w531w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1ab
0xb1dbf0…c0d3
8 touches
6 conflicts
0xa29182a1…c12c
0x34b655…2a6f
8 touches
6 conflicts
0xa3e06ffb…6c2b
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1aa
0xb1dbf0…c0d3
6 touches
3 conflicts
0x4c04ce68…d007
0x34b655…2a6f
6 touches
3 conflicts
0x750e6e4d…9dca
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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity