← previous blocknext block →recent activity
Analyzing
Block #96,599,965
14 transactions · 13 stateful · 2026-08-16 21:42:41 UTC
Parallelism
43/100
Blocked
54%
Avg conflicts / tx
1.64
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,599,965 · 14 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w38w49w510w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x0f6aef87…8137
0x34b655…2a6f
10 touches
10 conflicts
0xfb4a9740…bed8
0x34b655…2a6f
6 touches
3 conflicts
0x588380ee…0a5c
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x840d3ab7…c8c4
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity