← previous blocknext block →recent activity
Analyzing
Block #97,397,940
38 transactions · 38 stateful · 2026-08-19 17:19:44 UTC
Parallelism
82/100
Blocked
47%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,397,940 · 38 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w17w28w09w010w011w112w213w315w419w320w222w228w329w130w231w335w536w637w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57a454d0…d63e
0x34b655…2a6f
10 touches
10 conflicts
0xd71a331e…42ea
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x1f8a126c…9aa7
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
10 conflicts on slot 0x57a454d0c6…e9d63e
Audit this contract →
← previous block·next block →recent activity