← previous blocknext block →recent activity
Analyzing
Block #97,674,327
37 transactions · 37 stateful · 2026-08-20 16:42:15 UTC
Parallelism
57/100
Blocked
62%
Avg conflicts / tx
2
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #97,674,327 · 37 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w07w08w19w110w211w212w314w419w721w222w123w826w230w1033w1334w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ed00f98…da9f
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0x1eec16a0…9e8c
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
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
21 conflicts on slot 0x2ed00f9866…11da9f
Audit this contract →
← previous block·next block →recent activity