← previous blocknext block →recent activity
Analyzing
Block #97,529,697
25 transactions · 23 stateful · 2026-08-20 04:24:33 UTC
Parallelism
76/100
Blocked
43%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,529,697 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w07w19w110w211w312w313w414w015w118w223w524w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1dc86774…166a
0x34b655…2a6f
10 touches
10 conflicts
0x8902ba1f…f4b6
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x1203ea08…52c3
0xa6afd3…d132
6 touches
3 conflicts
0x12070f84…331c
0xa6afd3…d132
6 touches
3 conflicts
0x18865c9d…8ced
0xa6afd3…d132
6 touches
3 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
4 touches
1 conflict
0xdb067026…9eb8
0x2b46c0…1669
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
10 conflicts on slot 0x1dc86774a8…36166a
Audit this contract →
← previous block·next block →recent activity