← previous blocknext block →recent activity
Analyzing
Block #97,567,051
34 transactions · 31 stateful · 2026-08-20 07:34:01 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.56
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,567,051 · 34 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w09w111w012w313w414w515w516w617w018w126w127w131w032w133w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc38a1e34…37c3
0x34b655…2a6f
8 touches
6 conflicts
0xdfb18674…a680
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xd5a25205…6459
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
6 conflicts on slot 0xc38a1e3492…2d37c3
Audit this contract →
← previous block·next block →recent activity