← previous blocknext block →recent activity
Analyzing
Block #86,629,770
69 transactions · 46 stateful · 2026-07-09 13:12:33 UTC
Parallelism
71/100
Blocked
74%
Avg conflicts / tx
2.84
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #86,629,770 · 69 txs across 20 waves · depth 20
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
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w07w09w011w113w214w316w417w518w647w148w549w752w654w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0x70ff9262…8d80
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
14 touches
21 conflicts
0x00000000…00c9
0x34b655…2a6f
14 touches
21 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
12 touches
15 conflicts
0x15a8dcd6…2c36
0x34b655…2a6f
12 touches
15 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
12 touches
15 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
78 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity