← previous blocknext block →recent activity
Analyzing
Block #97,385,622
39 transactions · 34 stateful · 2026-08-19 16:02:40 UTC
Parallelism
77/100
Blocked
53%
Avg conflicts / tx
1.31
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #97,385,622 · 39 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w09w010w112w113w214w315w418w519w620w127w228w329w430w236w637w738w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x967ba723…6d0f
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0xa0bd005c…fd02
0xa6afd3…d132
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x9f608e7b…0b4e
0xa6afd3…d132
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: Perpl
10 conflicts on slot 0x967ba7239d…2d6d0f
Audit this contract →
← previous block·next block →recent activity