← previous blocknext block →recent activity
Analyzing
Block #95,796,486
23 transactions · 22 stateful · 2026-08-14 02:20:37 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.39
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,796,486 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w27w311w412w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x300c3654…ffc4
0x34b655…2a6f
12 touches
15 conflicts
0x96562bca…f07c
0x34b655…2a6f
8 touches
6 conflicts
0x4efae872…6aa8
0x34b655…2a6f
8 touches
6 conflicts
0x4f394483…ff62
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x574628e9…dcc3
0x34b655…2a6f
6 touches
3 conflicts
0x9a8af3c2…e4ae
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
15 conflicts on slot 0x300c36545f…eaffc4
Audit this contract →
← previous block·next block →recent activity