← previous blocknext block →recent activity
Analyzing
Block #86,621,240
23 transactions · 18 stateful · 2026-07-09 12:15:36 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
1.61
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,621,240 · 23 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
1w03w04w15w26w37w411w112w513w614w721w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
10 touches
10 conflicts
0x22bc4ea4…5c8a
0x34b655…2a6f
10 touches
10 conflicts
0x6b2ba712…0214
0x34b655…2a6f
10 touches
10 conflicts
0x2df1d4e5…f537
0x34b655…2a6f
8 touches
6 conflicts
0x2f6698be…af57
0x34b655…2a6f
8 touches
6 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
8 touches
6 conflicts
0x511ecf07…8ed0
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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity