← previous blocknext block →recent activity
Analyzing
Block #86,635,313
52 transactions · 43 stateful · 2026-07-09 13:49:38 UTC
Parallelism
69/100
Blocked
72%
Avg conflicts / tx
2.21
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #86,635,313 · 52 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w17w08w19w210w315w016w118w019w120w221w323w424w525w626w731w333w435w237w538w639w151w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x02991b41…19e6
0x34b655…2a6f
14 touches
21 conflicts
0xa29182a1…c12c
0x34b655…2a6f
12 touches
15 conflicts
0x1941b441…5889
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1a6
0xb1dbf0…c0d3
8 touches
6 conflicts
0xb43dc900…22f2
0xa6afd3…d132
8 touches
6 conflicts
0x7c78a77e…e55c
0xd32edf…ff58
7 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