← previous blocknext block →recent activity
Analyzing
Block #97,502,678
18 transactions · 17 stateful · 2026-08-20 02:08:37 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,502,678 · 18 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
1w02w13w24w06w38w09w110w212w313w414w517w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f33f3d3…2219
0x34b655…2a6f
10 touches
10 conflicts
0x21ca7579…1a1e
0x34b655…2a6f
8 touches
6 conflicts
0xd6f857b1…bae3
0x34b655…2a6f
6 touches
3 conflicts
0x398c19c9…ec59
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21bf
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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
10 conflicts on slot 0x3f33f3d387…2e2219
Audit this contract →
← previous block·next block →recent activity