← previous blocknext block →recent activity
Analyzing
Block #97,384,196
111 transactions · 99 stateful · 2026-08-19 15:52:26 UTC
Parallelism
82/100
Blocked
79%
Avg conflicts / tx
3.79
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #97,384,196 · 111 txs across 20 waves · depth 20
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
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w421w144w346w448w650w755w657w767w968w1069w1070w1180w1283w1385w14108w19
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
24 touches
66 conflicts
0xec7d120d…7084
0x34b655…2a6f
22 touches
55 conflicts
0x482471ad…122f
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…0002
0x103de0…bb55
22 touches
55 conflicts
0x889d5e90…929a
0x2a68ba…90c5
18 touches
36 conflicts
0x00000000…003d
0x40c49f…2af0
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…00c9
0x34b655…2a6f
16 touches
28 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
66 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity