← previous blocknext block →recent activity
Analyzing
Block #97,557,359
20 transactions · 16 stateful · 2026-08-20 06:44:31 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,557,359 · 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
1w02w04w05w16w17w28w29w313w117w418w519w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75fe24d2…46f9
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x275ce6ab…730a
0x34b655…2a6f
4 touches
1 conflict
0x548715b0…bda2
0x34b655…2a6f
4 touches
1 conflict
0x886db264…846e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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
15 conflicts on slot 0x75fe24d2da…6846f9
Audit this contract →
← previous block·next block →recent activity