← previous blocknext block →recent activity
Analyzing
Block #97,529,914
18 transactions · 16 stateful · 2026-08-20 04:25:39 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.61
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,529,914 · 18 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
1w04w06w07w08w19w110w111w212w216w217w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x640e6e56…63cc
0x34b655…2a6f
6 touches
3 conflicts
0x25d909da…1722
0x34b655…2a6f
6 touches
3 conflicts
0xef02ed46…48a4
0x34b655…2a6f
6 touches
3 conflicts
0x4c6e9f75…ffd2
0x34b655…2a6f
4 touches
1 conflict
0x76ef8464…e74b
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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity