← previous blocknext block →recent activity
Analyzing
Block #97,560,093
14 transactions · 13 stateful · 2026-08-20 06:58:30 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,560,093 · 14 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
3w06w07w18w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa397f471…08d6
0x8964d7…10f8
6 touches
3 conflicts
0xfd2417db…aa66
0x8964d7…10f8
6 touches
3 conflicts
0xfd2417db…aa64
0x8964d7…10f8
6 touches
3 conflicts
0xfd2417db…aa63
0x8964d7…10f8
6 touches
3 conflicts
0xfd2417db…aa60
0x8964d7…10f8
6 touches
3 conflicts
0xfd2417db…aa5f
0x8964d7…10f8
6 touches
3 conflicts
0xa397f471…08d9
0x8964d7…10f8
6 touches
3 conflicts
0xa397f471…08d7
0x8964d7…10f8
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: 0x8964d7c9…5b10f8
3 conflicts on slot 0xa397f471b0…d908d6
Audit this contract →
← previous block·next block →recent activity