← previous blocknext block →recent activity
Analyzing
Block #97,604,310
40 transactions · 37 stateful · 2026-08-20 10:42:21 UTC
Parallelism
68/100
Blocked
65%
Avg conflicts / tx
1.8
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #97,604,310 · 40 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
1w02w13w24w05w08w39w010w111w112w213w314w415w516w617w718w822w324w925w1026w1131w233w138w1239w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80eee557…711d
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xcc9d4fca…ecbf
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x511f46a7…edaa
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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 0x80eee55732…76711d
Audit this contract →
← previous block·next block →recent activity