← previous blocknext block →recent activity
Analyzing
Block #95,975,905
9 transactions · 7 stateful · 2026-08-14 17:23:24 UTC
Parallelism
44/100
Blocked
57%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,975,905 · 9 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
2w03w15w26w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x361a8fe7…6946
0x34b655…2a6f
8 touches
6 conflicts
0x745a7fd6…5fea
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x0ff353ce…a594
0x34b655…2a6f
6 touches
3 conflicts
0x5e2ea201…12de
0x34b655…2a6f
4 touches
1 conflict
0x784eaad2…d176
0x34b655…2a6f
4 touches
1 conflict
0x7caee600…f8b3
0x34b655…2a6f
4 touches
1 conflict
0x83f87246…1d5f
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 0x361a8fe746…246946
Audit this contract →
← previous block·next block →recent activity