← previous blocknext block →recent activity
Analyzing
Block #97,897,796
20 transactions · 19 stateful · 2026-08-21 11:38:25 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,897,796 · 20 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
1w02w13w04w15w07w18w29w210w012w213w316w317w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81ceb686…4df3
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x801a6e57…d85c
0x34b655…2a6f
4 touches
1 conflict
0xb34210fb…534f
0x34b655…2a6f
4 touches
1 conflict
0xb4651bf0…4cdf
0x34b655…2a6f
4 touches
1 conflict
0xb63ef486…0dcc
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 0x81ceb68611…284df3
Audit this contract →
← previous block·next block →recent activity