← previous blocknext block →recent activity
Analyzing
Block #97,369,263
22 transactions · 19 stateful · 2026-08-19 14:34:14 UTC
Parallelism
73/100
Blocked
42%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,369,263 · 22 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
2w03w15w06w17w28w39w313w414w521w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x379dc435…6616
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x02213185…bc8d
0x34b655…2a6f
8 touches
6 conflicts
0xbe54b7d5…1bda
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x1e67aecf…944e
0x34b655…2a6f
6 touches
3 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x379dc43545…336616
Audit this contract →
← previous block·next block →recent activity