← previous blocknext block →recent activity
Analyzing
Block #86,609,362
68 transactions · 53 stateful · 2026-07-09 10:56:19 UTC
Parallelism
69/100
Blocked
83%
Avg conflicts / tx
3.22
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #86,609,362 · 68 txs across 21 waves · depth 21
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
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w08w19w110w211w312w413w538w640w743w344w146w249w752w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
30 touches
105 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
16 touches
28 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
14 touches
21 conflicts
0x63c900f4…2600
0x34b655…2a6f
14 touches
21 conflicts
0x727fbce7…0c80
0x34b655…2a6f
14 touches
21 conflicts
0x9138a113…0d5f
0x34b655…2a6f
14 touches
21 conflicts
0x9966da31…0d0f
0x34b655…2a6f
14 touches
21 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
105 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity