← previous blocknext block →recent activity
Analyzing
Block #97,479,912
30 transactions · 23 stateful · 2026-08-20 00:14:06 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.07
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #97,479,912 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w19w010w311w412w513w615w717w321w822w923w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x806c6904…3d63
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x5bdbeef8…e5f4
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xf58eca50…59f6
0x1b6862…e19c
6 touches
3 conflicts
0x015a51cb…b7b7
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
15 conflicts on slot 0x806c6904e3…af3d63
Audit this contract →
← previous block·next block →recent activity