← previous blocknext block →recent activity
Analyzing
Block #86,319,286
91 transactions · 64 stateful · 2026-07-08 02:36:14 UTC
Parallelism
78/100
Blocked
75%
Avg conflicts / tx
3.86
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #86,319,286 · 91 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
1w02w13w24w35w46w57w617w127w928w1030w1135w1238w1340w1460w1667w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
38 touches
171 conflicts
0x62c0ea6a…45cb
0xd32edf…ff58
29 touches
105 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x00000000…003d
0xa6afd3…d132
18 touches
36 conflicts
0xb43dc900…22f2
0xa6afd3…d132
18 touches
36 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
16 touches
28 conflicts
0x7e10454f…4d9e
0xa6afd3…d132
16 touches
28 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
16 touches
28 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: Kuru Exchange: MarginAccount
171 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity