← previous blocknext block →recent activity
Analyzing
Block #96,033,739
13 transactions · 10 stateful · 2026-08-14 22:14:28 UTC
Parallelism
77/100
Blocked
50%
Avg conflicts / tx
0.54
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,033,739 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w16w28w212w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65f773b6…46cc
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
4 touches
1 conflict
0xe73b93bf…c0e1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcb0221be…c2b3
0x34b655…2a6f
4 touches
1 conflict
0x3e3b859f…3654
0x34b655…2a6f
2 touches
0 conflicts
0x748ce49f…a12c
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x65f773b6cf…ef46cc
Audit this contract →
← previous block·next block →recent activity