← previous blocknext block →recent activity
Analyzing
Block #96,605,524
17 transactions · 16 stateful · 2026-08-16 22:10:39 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.18
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,605,524 · 17 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
2w03w04w15w26w27w18w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69656781…3c53
0x34b655…2a6f
8 touches
6 conflicts
0x26ec135b…9718
0x34b655…2a6f
6 touches
3 conflicts
0x0f6aef87…8137
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
6 touches
3 conflicts
0x038b9243…553d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x69656781f9…343c53
Audit this contract →
← previous block·next block →recent activity