← previous blocknext block →recent activity
Analyzing
Block #91,071,931
74 transactions · 56 stateful · 2026-07-28 13:39:44 UTC
Parallelism
65/100
Blocked
84%
Avg conflicts / tx
5.34
Longest chain
26 deep
Execution timeline
did this block parallelize well?
view
block #91,071,931 · 74 txs across 26 waves · depth 26
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
wave w21
wave w22
wave w23
wave w24
wave w25
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w49w010w534w2335w537w154w660w24
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
50 touches
300 conflicts
0xfa551be3…a911
0xa6afd3…d132
44 touches
231 conflicts
0x00000000…003d
0xa6afd3…d132
44 touches
231 conflicts
0x3de775b2…319b
0xa6afd3…d132
44 touches
231 conflicts
0xdb067026…9eb8
0x2b46c0…1669
42 touches
210 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
42 touches
210 conflicts
0x40970e69…da50
0x2b46c0…1669
42 touches
210 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
42 touches
210 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
300 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity