← previous blocknext block →recent activity
Analyzing
Block #97,518,177
18 transactions · 17 stateful · 2026-08-20 03:26:37 UTC
Parallelism
72/100
Blocked
53%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,518,177 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w17w28w211w212w315w417w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda9d71aa…e43f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xec85b41e…7c91
0x1b6862…e19c
4 touches
1 conflict
0x1ba73d09…ba89
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 0xda9d71aa15…4de43f
Audit this contract →
← previous block·next block →recent activity