← previous blocknext block →recent activity
Analyzing
Block #86,663,363
25 transactions · 22 stateful · 2026-07-09 16:58:15 UTC
Parallelism
60/100
Blocked
59%
Avg conflicts / tx
1.8
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,663,363 · 25 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
2w03w16w07w18w29w311w412w513w614w415w616w719w123w824w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0xe6805ef8…e22e
0x34b655…2a6f
12 touches
15 conflicts
0x8a35acfb…d1ab
0xb1dbf0…c0d3
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x9de5869c…6ca5
0x34b655…2a6f
6 touches
3 conflicts
0x9365e097…ff56
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