← previous blocknext block →recent activity
Analyzing
Block #96,275,206
17 transactions · 16 stateful · 2026-08-15 18:29:00 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,275,206 · 17 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
1w02w14w05w06w111w212w313w414w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9dd0a735…4d04
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xea8fb2fb…8dd2
0x34b655…2a6f
7 touches
6 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0xfcecce2a…149c
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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
6 conflicts on slot 0x9dd0a735d4…464d04
Audit this contract →
← previous block·next block →recent activity