← previous blocknext block →recent activity
Analyzing
Block #97,522,134
21 transactions · 18 stateful · 2026-08-20 03:46:31 UTC
Parallelism
71/100
Blocked
39%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,522,134 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w07w08w39w411w118w520w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x25ff7717…d4af
0x34b655…2a6f
8 touches
6 conflicts
0x88dd8d47…6608
0xd32edf…ff58
7 touches
6 conflicts
0x21d8e673…067a
0x1b6862…e19c
6 touches
3 conflicts
0x8a3fee63…78d0
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
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
6 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity