← previous blocknext block →recent activity
Analyzing
Block #97,566,308
25 transactions · 24 stateful · 2026-08-20 07:30:14 UTC
Parallelism
80/100
Blocked
58%
Avg conflicts / tx
0.96
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,566,308 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w27w38w09w010w111w112w313w114w216w219w320w321w424w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6f857b1…bae3
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c1
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
6 conflicts on slot 0xd6f857b1e7…f4bae3
Audit this contract →
← previous block·next block →recent activity