← previous blocknext block →recent activity
Analyzing
Block #86,664,913
24 transactions · 23 stateful · 2026-07-09 17:08:37 UTC
Parallelism
58/100
Blocked
52%
Avg conflicts / tx
1.5
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,664,913 · 24 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
1w02w03w14w25w36w47w58w614w717w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x06aed19e…ca57
0x34b655…2a6f
10 touches
10 conflicts
0x2d7ea048…d78e
0x34b655…2a6f
10 touches
10 conflicts
0x89c7ec3b…85ba
0x34b655…2a6f
10 touches
10 conflicts
0xa1571d54…ae41
0x34b655…2a6f
10 touches
10 conflicts
0xb485663b…cb5a
0x34b655…2a6f
10 touches
10 conflicts
0xc368d7fd…aaec
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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity