← previous blocknext block →recent activity
Analyzing
Block #97,503,560
17 transactions · 17 stateful · 2026-08-20 02:13:04 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,503,560 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w06w17w28w310w414w015w516w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0099420d…37b4
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
3 conflicts
0x80a49a52…b8af
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x5d1ac445…5233
0x34b655…2a6f
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
15 conflicts on slot 0x0099420dea…e337b4
Audit this contract →
← previous block·next block →recent activity