← previous blocknext block →recent activity
Analyzing
Block #97,898,189
18 transactions · 18 stateful · 2026-08-21 11:40:24 UTC
Parallelism
78/100
Blocked
39%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,898,189 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w06w17w08w110w211w313w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2528e717…2a22
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xebb541cb…a721
0xa6afd3…d132
6 touches
3 conflicts
0xced85967…4103
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21bf
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
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
3 conflicts on slot 0x2528e7175c…302a22
Audit this contract →
← previous block·next block →recent activity