← previous blocknext block →recent activity
Analyzing
Block #97,558,596
35 transactions · 35 stateful · 2026-08-20 06:50:50 UTC
Parallelism
63/100
Blocked
69%
Avg conflicts / tx
2.49
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #97,558,596 · 35 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w07w08w19w110w111w212w213w314w315w416w517w518w622w323w424w626w127w131w1032w1133w1234w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
14 touches
21 conflicts
0x728f999a…832f
0x34b655…2a6f
14 touches
21 conflicts
0x275ce6ab…730a
0x34b655…2a6f
12 touches
15 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 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 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity