← previous blocknext block →recent activity
Analyzing
Block #91,409,694
67 transactions · 35 stateful · 2026-07-29 18:00:21 UTC
Parallelism
84/100
Blocked
74%
Avg conflicts / tx
0.9
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #91,409,694 · 67 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w17w018w127w030w131w232w334w435w537w638w745w855w1056w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x5502e1cc…3910
0x34b655…2a6f
10 touches
10 conflicts
0x4f1ad4b4…e00a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x66a11a3b…0ee9
0xa6afd3…d132
8 touches
6 conflicts
0xb566cc65…214d
0xa6afd3…d132
8 touches
6 conflicts
0xac2a0273…721b
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
15 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity