← previous blocknext block →recent activity
Analyzing
Block #97,612,766
16 transactions · 16 stateful · 2026-08-20 11:25:28 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,612,766 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w06w17w28w110w211w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17f192de…765e
0x34b655…2a6f
8 touches
6 conflicts
0x88724b87…5e65
0x34b655…2a6f
6 touches
3 conflicts
0x33ab074d…528d
0x34b655…2a6f
6 touches
3 conflicts
0x2e5cdd04…22ab
0x34b655…2a6f
6 touches
3 conflicts
0xd2f60a4a…2910
0xd32edf…ff58
5 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xcaced930…08b5
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
6 conflicts on slot 0x17f192de5b…37765e
Audit this contract →
← previous block·next block →recent activity