← previous blocknext block →recent activity
Analyzing
Block #97,546,008
24 transactions · 21 stateful · 2026-08-20 05:46:36 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,546,008 · 24 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
1w03w09w010w113w114w015w116w217w218w019w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x092a49af…5d6a
0x8964d7…10f8
6 touches
3 conflicts
0x092a49af…5d6c
0x8964d7…10f8
6 touches
3 conflicts
0xd89ec960…85ce
0x8964d7…10f8
6 touches
3 conflicts
0xd89ec960…85cf
0x8964d7…10f8
6 touches
3 conflicts
0xd89ec960…85d2
0x8964d7…10f8
6 touches
3 conflicts
0xd89ec960…85d3
0x8964d7…10f8
6 touches
3 conflicts
0xd89ec960…85d4
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: Perpl
3 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity