← previous blocknext block →recent activity
Analyzing
Block #97,554,634
21 transactions · 19 stateful · 2026-08-20 06:30:42 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,554,634 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w07w08w19w210w012w313w414w116w517w620w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf80e177…646c
0x34b655…2a6f
8 touches
6 conflicts
0x8902ba1f…f4b6
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x806c6904…3d63
0x34b655…2a6f
4 touches
1 conflict
0x8fee2b50…f8c7
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 0xcf80e1776a…ee646c
Audit this contract →
← previous block·next block →recent activity