← previous blocknext block →recent activity
Analyzing
Block #96,837,769
15 transactions · 13 stateful · 2026-08-17 17:38:45 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,837,769 · 15 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
1w03w04w15w28w39w410w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x29418a3d…8c6e
0x34b655…2a6f
8 touches
6 conflicts
0xd8bc53a3…c2fe
0x34b655…2a6f
8 touches
6 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xe316a1f9…1966
0x34b655…2a6f
6 touches
3 conflicts
0x4cb99d90…9680
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity