← previous blocknext block →recent activity
Analyzing
Block #86,084,718
61 transactions · 46 stateful · 2026-07-07 00:30:04 UTC
Parallelism
69/100
Blocked
74%
Avg conflicts / tx
3.13
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #86,084,718 · 61 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w713w618w824w1225w1342w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
24 touches
66 conflicts
0xb450e18d…576e
0xd32edf…ff58
23 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x7f4a8466…f2cc
0x69df8a…6292
16 touches
28 conflicts
0xae5e6f9a…2991
0xc8689a…ee79
16 touches
28 conflicts
0x00000000…003d
0x40c49f…2af0
16 touches
28 conflicts
0x46279ae7…20dd
0x69df8a…6292
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
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: Kuru Exchange: MarginAccount
66 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity