← previous blocknext block →recent activity
Analyzing
Block #97,480,370
30 transactions · 25 stateful · 2026-08-20 00:16:24 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,480,370 · 30 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
1w02w13w24w25w38w09w010w111w212w013w014w116w317w324w425w329w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x806c6904…3d63
0x34b655…2a6f
10 touches
10 conflicts
0xb873dc93…2a8f
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0x10c19272…743f
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 0x806c6904e3…af3d63
Audit this contract →
← previous block·next block →recent activity