← previous blocknext block →recent activity
Analyzing
Block #97,628,579
34 transactions · 28 stateful · 2026-08-20 12:45:02 UTC
Parallelism
71/100
Blocked
57%
Avg conflicts / tx
1.32
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #97,628,579 · 34 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
1w02w13w07w18w29w310w418w519w620w721w822w929w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
14 touches
21 conflicts
0xce4db664…9af1
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…001b
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
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