← previous blocknext block →recent activity
Analyzing
Block #91,410,236
50 transactions · 40 stateful · 2026-07-29 18:03:05 UTC
Parallelism
74/100
Blocked
70%
Avg conflicts / tx
1.9
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #91,410,236 · 50 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w59w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xc0b73a72…d549
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…001f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
10 touches
10 conflicts
0x4979282b…2938
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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
21 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity