← previous blocknext block →recent activity
Analyzing
Block #96,261,722
14 transactions · 14 stateful · 2026-08-15 17:21:11 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.93
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,261,722 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w07w18w39w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xabf57eb6…416d
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xa5a8ffca…8de2
0x34b655…2a6f
10 touches
10 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
8 touches
6 conflicts
0x784eaad2…d176
0x34b655…2a6f
8 touches
6 conflicts
0xca995928…ded0
0x34b655…2a6f
8 touches
6 conflicts
0x28e058b0…91e9
0x34b655…2a6f
7 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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity