← previous blocknext block →recent activity
Analyzing
Block #97,385,991
92 transactions · 72 stateful · 2026-08-19 16:05:24 UTC
Parallelism
80/100
Blocked
63%
Avg conflicts / tx
1.46
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #97,385,991 · 92 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w17w28w213w014w115w216w317w418w519w620w721w225w650w764w876w977w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x103de0…bb55
16 touches
28 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0x9afde83d…0318
0xa6afd3…d132
12 touches
15 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x3199a6b2…eb67
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xcb1683de…7afe
0x34b655…2a6f
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: 0x103de0b5…25bb55
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity