← previous blocknext block →recent activity
Analyzing
Block #97,665,333
88 transactions · 74 stateful · 2026-08-20 15:55:44 UTC
Parallelism
80/100
Blocked
69%
Avg conflicts / tx
2.89
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #97,665,333 · 88 txs across 18 waves · depth 18
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
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w420w226w127w228w330w431w532w533w637w839w940w1049w953w456w1260w1163w1366w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
20 touches
45 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x40ac662f…df77
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x02b4abec…397d
0x34b655…2a6f
14 touches
21 conflicts
0x157b6348…8604
0x34b655…2a6f
12 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 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
45 conflicts on slot 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity