← previous blocknext block →recent activity
Analyzing
Block #97,718,297
20 transactions · 20 stateful · 2026-08-20 20:25:55 UTC
Parallelism
75/100
Blocked
45%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,718,297 · 20 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
1w02w06w07w18w09w110w011w212w313w415w116w118w419w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3076829…033c
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xd4a01a03…6e3d
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x72ec2001…6792
0x40c49f…2af0
4 touches
1 conflict
0x7e73d794…7a6b
0x40c49f…2af0
4 touches
1 conflict
0xb4b9ad8d…e25f
0x40c49f…2af0
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 0xa307682937…e4033c
Audit this contract →
← previous block·next block →recent activity