← previous blocknext block →recent activity
Analyzing
Block #97,612,260
33 transactions · 33 stateful · 2026-08-20 11:22:55 UTC
Parallelism
82/100
Blocked
39%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,612,260 · 33 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
1w02w13w24w06w17w08w29w310w311w212w314w417w418w420w532w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad525cb3…1b17
0x34b655…2a6f
10 touches
10 conflicts
0x40ac662f…df77
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0x58e06bab…34ce
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x62a0cf8a…48b4
0x34b655…2a6f
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
10 conflicts on slot 0xad525cb34f…ad1b17
Audit this contract →
← previous block·next block →recent activity