← previous blocknext block →recent activity
Analyzing
Block #97,511,318
39 transactions · 35 stateful · 2026-08-20 02:52:06 UTC
Parallelism
56/100
Blocked
66%
Avg conflicts / tx
2.15
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #97,511,318 · 39 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w09w010w111w112w213w214w315w417w518w626w127w1028w229w334w1338w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0304ed8a…9f25
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x85054dde…45f1
0x34b655…2a6f
8 touches
6 conflicts
0x8902ba1f…f4b6
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 0x0304ed8a79…3f9f25
Audit this contract →
← previous block·next block →recent activity