← previous blocknext block →recent activity
Analyzing
Block #97,197,592
23 transactions · 22 stateful · 2026-08-19 00:01:44 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,197,592 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w08w19w210w311w012w113w216w119w020w122w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x11b69a7e…334e
0xee8c0e…1242
6 touches
3 conflicts
0x2a9e9bd1…5368
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x5f64baf0…fae7
0xa6afd3…d132
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity