← previous blocknext block →recent activity
Analyzing
Block #95,738,333
26 transactions · 24 stateful · 2026-08-13 21:28:09 UTC
Parallelism
77/100
Blocked
29%
Avg conflicts / tx
0.54
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,738,333 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w19w210w311w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa69b7638…7f86
0x34b655…2a6f
8 touches
6 conflicts
0x620b761c…270e
0x34b655…2a6f
6 touches
3 conflicts
0x9a3068dd…18f1
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x31d88d27…7617
0x34b655…2a6f
4 touches
1 conflict
0x42c0a5d3…a476
0x34b655…2a6f
4 touches
1 conflict
0x60dc7b78…d1d5
0x34b655…2a6f
4 touches
1 conflict
0x8ce5fb99…20fa
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
6 conflicts on slot 0xa69b763841…4f7f86
Audit this contract →
← previous block·next block →recent activity