← previous blocknext block →recent activity
Analyzing
Block #96,562,115
20 transactions · 15 stateful · 2026-08-16 18:32:19 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,562,115 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w08w19w210w011w112w213w214w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x466c9e6a…e9de
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xafb8e71e…9285
0x34b655…2a6f
6 touches
3 conflicts
0x972e38eb…dc76
0x34b655…2a6f
6 touches
3 conflicts
0x3b689fd2…629c
0x34b655…2a6f
6 touches
3 conflicts
0xc5bcb446…c130
0xd32edf…ff58
5 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x8ac41992…cf98
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
3 conflicts on slot 0x466c9e6a9e…88e9de
Audit this contract →
← previous block·next block →recent activity