← previous blocknext block →recent activity
Analyzing
Block #97,604,158
32 transactions · 24 stateful · 2026-08-20 10:41:35 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,604,158 · 32 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
1w02w13w24w011w012w313w014w115w217w325w127w231w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x82187006…4dc6
0x34b655…2a6f
8 touches
6 conflicts
0x54fff8e6…eb6d
0xd32edf…ff58
7 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
0x4e7eb462…b2ac
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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 0x8218700610…3e4dc6
Audit this contract →
← previous block·next block →recent activity