← previous blocknext block →recent activity
Analyzing
Block #97,730,642
20 transactions · 19 stateful · 2026-08-20 21:28:21 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,730,642 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w17w08w19w210w211w313w417w218w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6c9bf9b…ac02
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x20299510…1261
0x34b655…2a6f
4 touches
1 conflict
0x280d1119…ee4d
0x34b655…2a6f
4 touches
1 conflict
0x2bd98ca9…fb14
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x69352f9f…5449
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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
6 conflicts on slot 0xf6c9bf9b65…e4ac02
Audit this contract →
← previous block·next block →recent activity