← previous blocknext block →recent activity
Analyzing
Block #97,674,032
18 transactions · 18 stateful · 2026-08-20 16:40:40 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,674,032 · 18 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
4w05w16w28w09w011w312w113w216w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x84720232…c5d1
0x34b655…2a6f
8 touches
6 conflicts
0xa38c430a…e3cb
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xdeaa385f…6b8b
0x34b655…2a6f
6 touches
3 conflicts
0xc00331b8…72ad
0x34b655…2a6f
6 touches
3 conflicts
0x7b45753f…3d76
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity