← previous blocknext block →recent activity
Analyzing
Block #95,540,217
27 transactions · 25 stateful · 2026-08-13 04:50:38 UTC
Parallelism
74/100
Blocked
48%
Avg conflicts / tx
1.26
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,540,217 · 27 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w38w39w412w416w017w122w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0xc306e51e…a103
0x968279…9342
8 touches
6 conflicts
0x2a54175b…524e
0x968279…9342
8 touches
6 conflicts
0x2a54175b…5250
0x968279…9342
8 touches
6 conflicts
0xc306e51e…a100
0x968279…9342
8 touches
6 conflicts
0xc306e51e…a101
0x968279…9342
8 touches
6 conflicts
0x66d5e476…8a1f
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity