← previous blocknext block →recent activity
Analyzing
Block #96,531,504
13 transactions · 13 stateful · 2026-08-16 15:58:21 UTC
Parallelism
54/100
Blocked
54%
Avg conflicts / tx
1.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,531,504 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w28w39w410w512w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1711d896…11a8
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xff196840…a453
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xc9ac06bf…7da5
0x34b655…2a6f
8 touches
6 conflicts
0x9c2fc330…0091
0x34b655…2a6f
6 touches
3 conflicts
0x28f324ed…9db7
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
15 conflicts on slot 0x1711d896ac…3d11a8
Audit this contract →
← previous block·next block →recent activity