← previous blocknext block →recent activity
Analyzing
Block #95,373,716
21 transactions · 17 stateful · 2026-08-12 14:51:34 UTC
Parallelism
86/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,373,716 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w07w08w112w115w016w217w118w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a42683d…6f4f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x42de1b4a…7fba
0x34b655…2a6f
6 touches
3 conflicts
0xb83ac6e4…3637
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x947bb79d…6458
0x34b655…2a6f
6 touches
3 conflicts
0xa8384cd8…1538
0x34b655…2a6f
5 touches
3 conflicts
0xef61a0a1…3168
0xd32edf…ff58
5 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
3 conflicts on slot 0x0a42683dda…f36f4f
Audit this contract →
← previous block·next block →recent activity