← previous blocknext block →recent activity
Analyzing
Block #95,151,523
20 transactions · 18 stateful · 2026-08-11 20:01:59 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,151,523 · 20 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
1w02w13w25w37w08w09w111w212w313w418w019w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x602f6bee…27ad
0xd32edf…ff58
7 touches
6 conflicts
0x966e45cf…0f25
0x34b655…2a6f
6 touches
3 conflicts
0x763104af…f44e
0x34b655…2a6f
4 touches
1 conflict
0x89999c15…fdac
0x34b655…2a6f
4 touches
1 conflict
0x8cd684d0…c3cb
0x34b655…2a6f
4 touches
1 conflict
0x9a9383a9…6bc7
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity