← previous blocknext block →recent activity
Analyzing
Block #97,397,236
52 transactions · 50 stateful · 2026-08-19 17:16:09 UTC
Parallelism
69/100
Blocked
54%
Avg conflicts / tx
1.85
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #97,397,236 · 52 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w18w19w110w211w212w313w415w316w417w532w1143w744w1251w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9b377bf…8bc5
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x6f6aa736…a698
0x34b655…2a6f
10 touches
10 conflicts
0x4b4b264b…cd5e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xc9b377bf55…c48bc5
Audit this contract →
← previous block·next block →recent activity