← previous blocknext block →recent activity
Analyzing
Block #96,665,961
14 transactions · 12 stateful · 2026-08-17 03:14:37 UTC
Parallelism
50/100
Blocked
58%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,665,961 · 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
1w02w13w24w25w39w410w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2ca9bf2…8da8
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0xfbe6a366…8ca1
0x34b655…2a6f
8 touches
6 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
6 touches
3 conflicts
0x444432b3…8b3d
0x34b655…2a6f
6 touches
3 conflicts
0xd8abfb71…2ff4
0x34b655…2a6f
5 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
6 conflicts on slot 0xe2ca9bf21a…2c8da8
Audit this contract →
← previous block·next block →recent activity