← previous blocknext block →recent activity
Analyzing
Block #97,569,024
24 transactions · 22 stateful · 2026-08-20 07:44:03 UTC
Parallelism
75/100
Blocked
45%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,569,024 · 24 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
1w02w03w16w07w18w012w013w214w315w216w117w321w422w523w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf80e177…646c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x345024b2…b357
0x34b655…2a6f
6 touches
3 conflicts
0x4fc16b3f…e1b9
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x81ca8c9e…28cb
0x34b655…2a6f
4 touches
1 conflict
0x9e435fce…d1de
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
3 conflicts on slot 0xcf80e1776a…ee646c
Audit this contract →
← previous block·next block →recent activity