← previous blocknext block →recent activity
Analyzing
Block #96,017,176
13 transactions · 10 stateful · 2026-08-14 20:51:07 UTC
Parallelism
54/100
Blocked
50%
Avg conflicts / tx
1.08
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,017,176 · 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
1w02w13w25w07w38w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31616f97…1acc
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc9c2f132…25f2
0x34b655…2a6f
6 touches
3 conflicts
0xd6113c0f…0a4b
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x56153262…21ce
0x34b655…2a6f
4 touches
1 conflict
0xb9a63764…f004
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 0x31616f9701…df1acc
Audit this contract →
← previous block·next block →recent activity