← previous blocknext block →recent activity
Analyzing
Block #97,668,899
42 transactions · 40 stateful · 2026-08-20 16:14:07 UTC
Parallelism
67/100
Blocked
70%
Avg conflicts / tx
1.93
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #97,668,899 · 42 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w08w09w110w111w212w313w414w415w516w617w721w824w925w1027w131w1132w234w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40ac662f…df77
0x34b655…2a6f
12 touches
15 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 conflicts
0xb4a95e21…8ec7
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
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
15 conflicts on slot 0x40ac662f45…43df77
Audit this contract →
← previous block·next block →recent activity