← previous blocknext block →recent activity
Analyzing
Block #97,656,301
39 transactions · 34 stateful · 2026-08-20 15:08:51 UTC
Parallelism
59/100
Blocked
56%
Avg conflicts / tx
2.28
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #97,656,301 · 39 txs across 16 waves · depth 16
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
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w18w09w011w012w113w214w315w416w517w618w619w727w1028w129w830w1134w1235w1337w1438w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
20 touches
45 conflicts
0x482471ad…122f
0x34b655…2a6f
20 touches
45 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0x89845743…6ee0
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x405b0651…4ef6
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
45 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity