← previous blocknext block →recent activity
Analyzing
Block #97,665,417
18 transactions · 18 stateful · 2026-08-20 15:56:09 UTC
Parallelism
78/100
Blocked
61%
Avg conflicts / tx
0.89
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,665,417 · 18 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
1w02w13w24w05w16w07w18w29w210w211w313w214w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0988d33…e5c6
0x34b655…2a6f
8 touches
6 conflicts
0xd75bf3ea…a62e
0x34b655…2a6f
6 touches
3 conflicts
0x04c5c873…dd0a
0xa6afd3…d132
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x45b67460…28a9
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0398c745…05d0
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 0xc0988d3373…01e5c6
Audit this contract →
← previous block·next block →recent activity