← previous blocknext block →recent activity
Analyzing
Block #97,671,229
30 transactions · 30 stateful · 2026-08-20 16:26:06 UTC
Parallelism
80/100
Blocked
57%
Avg conflicts / tx
1.23
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,671,229 · 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
1w02w13w24w16w37w08w19w010w011w112w213w214w315w319w322w523w528w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0x892daf6e…48d8
0x065c9d…c394
8 touches
6 conflicts
0xb99b689d…9ff1
0x34b655…2a6f
8 touches
6 conflicts
0x967a98d2…6d73
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
4 touches
1 conflict
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 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity