← previous blocknext block →recent activity
Analyzing
Block #91,409,629
115 transactions · 77 stateful · 2026-07-29 18:00:01 UTC
Parallelism
83/100
Blocked
78%
Avg conflicts / tx
2.9
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #91,409,629 · 115 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
2w013w115w216w218w019w020w121w122w023w124w227w333w440w141w242w045w146w271w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
40 touches
190 conflicts
0xb566cc65…214d
0xa6afd3…d132
22 touches
55 conflicts
0x00000000…003d
0xa6afd3…d132
22 touches
55 conflicts
0x5778d110…d2e6
0xc8689a…ee79
20 touches
45 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
20 touches
45 conflicts
0x40970e69…da50
0x2b46c0…1669
20 touches
45 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
20 touches
45 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
20 touches
45 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
190 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity