← previous blocknext block →recent activity
Analyzing
Block #97,384,768
34 transactions · 32 stateful · 2026-08-19 15:56:23 UTC
Parallelism
71/100
Blocked
59%
Avg conflicts / tx
1.5
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #97,384,768 · 34 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
2w04w15w06w17w08w09w110w111w212w213w314w315w418w319w421w633w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x967ba723…6d0f
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0x69458677…caaa
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd0239610…5596
0x34b655…2a6f
6 touches
3 conflicts
0x9fbc6a76…9c29
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 0x967ba7239d…2d6d0f
Audit this contract →
← previous block·next block →recent activity