← previous blocknext block →recent activity
Analyzing
Block #97,553,318
64 transactions · 55 stateful · 2026-08-20 06:23:53 UTC
Parallelism
73/100
Blocked
84%
Avg conflicts / tx
3
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #97,553,318 · 64 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
1w02w13w24w35w46w57w68w723w324w425w526w662w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3c91855…d0df
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0002
0x103de0…bb55
18 touches
36 conflicts
0xec7d120d…7084
0x34b655…2a6f
16 touches
28 conflicts
0x5380c346…c113
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0029
0x1b6862…e19c
14 touches
21 conflicts
0xc13fac9b…d2cf
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 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
36 conflicts on slot 0xa3c9185504…b5d0df
Audit this contract →
← previous block·next block →recent activity