← previous blocknext block →recent activity
Analyzing
Block #97,496,991
26 transactions · 25 stateful · 2026-08-20 01:40:01 UTC
Parallelism
85/100
Blocked
44%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,496,991 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w111w012w013w114w115w216w119w320w223w225w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x728f999a…832f
0x34b655…2a6f
6 touches
3 conflicts
0x8f0c33cf…6e73
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xcf80e177…646c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0xd5b10148…e631
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
3 conflicts on slot 0x728f999afb…4e832f
Audit this contract →
← previous block·next block →recent activity