← previous blocknext block →recent activity
Analyzing
Block #95,541,687
11 transactions · 7 stateful · 2026-08-13 04:58:01 UTC
Parallelism
64/100
Blocked
57%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,541,687 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0caa5e3f…ea20
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbc66586e…20fe
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x529e53cf…38e4
0xa6afd3…d132
4 touches
1 conflict
0x39cbc853…9a82
0x34b655…2a6f
4 touches
1 conflict
0x7d7c8caa…dc36
0x34b655…2a6f
4 touches
1 conflict
0x981b7617…6093
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
3 conflicts on slot 0x0caa5e3f90…fcea20
Audit this contract →
← previous block·next block →recent activity