← previous blocknext block →recent activity
Analyzing
Block #95,750,746
8 transactions · 8 stateful · 2026-08-13 22:30:35 UTC
Parallelism
50/100
Blocked
38%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,750,746 · 8 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
3w04w15w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b2d3bee…8eeb
0x34b655…2a6f
6 touches
3 conflicts
0x8cd684d0…c3cb
0x34b655…2a6f
6 touches
3 conflicts
0x0672e4a2…8d1f
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6636a104…d595
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x82622649…e56d
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 0x9b2d3bee9d…d68eeb
Audit this contract →
← previous block·next block →recent activity