← previous blocknext block →recent activity
Analyzing
Block #86,699,584
18 transactions · 15 stateful · 2026-07-09 20:59:58 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,699,584 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w412w113w214w217w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x89c7ec3b…85ba
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
8 touches
6 conflicts
0x4a8cbb6a…61cd
0x34b655…2a6f
8 touches
6 conflicts
0x548145a9…cfce
0x34b655…2a6f
8 touches
6 conflicts
0x63b15849…80b2
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity