← previous blocknext block →recent activity
Analyzing
Block #86,224,863
41 transactions · 36 stateful · 2026-07-07 16:05:42 UTC
Parallelism
76/100
Blocked
67%
Avg conflicts / tx
2.32
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,224,863 · 41 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w37w48w516w618w619w720w822w723w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xcd97439a…a1e2
0x065c9d…c394
7 touches
6 conflicts
0x4e3abeff…18eb
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
6 touches
3 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
36 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity