← previous blocknext block →recent activity
Analyzing
Block #96,622,969
14 transactions · 11 stateful · 2026-08-16 23:38:23 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
1.14
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,622,969 · 14 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
1w03w05w16w07w29w010w111w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee5aa5fa…ff8b
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbdbe6b59…f6d8
0x34b655…2a6f
8 touches
6 conflicts
0x0f6aef87…8137
0x34b655…2a6f
8 touches
6 conflicts
0xfc8cd993…5c11
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x56a284d9…32e4
0x34b655…2a6f
6 touches
3 conflicts
0xa4e9800f…4ab0
0x34b655…2a6f
6 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
10 conflicts on slot 0xee5aa5fad5…17ff8b
Audit this contract →
← previous block·next block →recent activity