← previous blocknext block →recent activity
Analyzing
Block #95,155,328
11 transactions · 11 stateful · 2026-08-11 20:21:07 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.91
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,155,328 · 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
2w03w04w06w17w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8cd684d0…c3cb
0x34b655…2a6f
8 touches
6 conflicts
0x1c93cd52…1538
0x34b655…2a6f
6 touches
3 conflicts
0x3b56f79b…310f
0x34b655…2a6f
6 touches
3 conflicts
0xfc8cd993…5c11
0x34b655…2a6f
6 touches
3 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x83f3d320…fb59
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
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 0x8cd684d0d7…f5c3cb
Audit this contract →
← previous block·next block →recent activity