← previous blocknext block →recent activity
Analyzing
Block #97,738,008
22 transactions · 21 stateful · 2026-08-20 22:05:24 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,738,008 · 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
1w02w03w05w06w17w28w39w410w512w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x280d1119…ee4d
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0f9b918b…212d
0x34b655…2a6f
6 touches
3 conflicts
0xf2353b70…5420
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0x280d1119b5…8aee4d
Audit this contract →
← previous block·next block →recent activity