← previous blocknext block →recent activity
Analyzing
Block #97,358,159
50 transactions · 44 stateful · 2026-08-19 13:37:13 UTC
Parallelism
72/100
Blocked
64%
Avg conflicts / tx
2.44
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #97,358,159 · 50 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w06w17w28w19w012w113w114w216w218w321w428w530w631w732w133w335w137w238w939w1040w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0x1cc683f9…4564
0x34b655…2a6f
12 touches
15 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 conflicts
0x9a3068dd…18f1
0x34b655…2a6f
10 touches
10 conflicts
0x69a45f39…39aa
0x34b655…2a6f
10 touches
10 conflicts
0x99c5409a…25b7
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…642d
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity