← previous blocknext block →recent activity
Analyzing
Block #97,605,183
47 transactions · 46 stateful · 2026-08-20 10:46:48 UTC
Parallelism
66/100
Blocked
67%
Avg conflicts / tx
2.36
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #97,605,183 · 47 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
1w04w05w16w27w18w39w010w111w112w213w214w315w316w417w418w519w620w725w737w238w346w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40ac662f…df77
0x34b655…2a6f
16 touches
28 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x95cdd21b…b6bc
0x34b655…2a6f
10 touches
10 conflicts
0x2e5cdd04…22ab
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x80eee557…711d
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
28 conflicts on slot 0x40ac662f45…43df77
Audit this contract →
← previous block·next block →recent activity