← previous blocknext block →recent activity
Analyzing
Block #97,989,618
13 transactions · 13 stateful · 2026-08-21 19:25:27 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,989,618 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w19w211w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcaa5e459…c7eb
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xf15273a1…2c52
0x34b655…2a6f
6 touches
3 conflicts
0x4f858307…7642
0x34b655…2a6f
4 touches
1 conflict
0x6762cac2…3fb0
0x34b655…2a6f
4 touches
1 conflict
0x7b641695…11f1
0x34b655…2a6f
4 touches
1 conflict
0x7db78f05…2895
0x34b655…2a6f
4 touches
1 conflict
0xa7fa69c0…2f32
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
3 conflicts on slot 0xcaa5e45985…ccc7eb
Audit this contract →
← previous block·next block →recent activity