← previous blocknext block →recent activity
Analyzing
Block #97,362,072
20 transactions · 20 stateful · 2026-08-19 13:57:30 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
1.55
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,362,072 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w17w28w19w210w311w412w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3383813…4a0c
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x46822f8c…d048
0x34b655…2a6f
10 touches
10 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xd03f3825…8b17
0x34b655…2a6f
5 touches
3 conflicts
0x00d80c6e…ab3b
0x34b655…2a6f
4 touches
2 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
28 conflicts on slot 0xf338381336…ec4a0c
Audit this contract →
← previous block·next block →recent activity