← previous blocknext block →recent activity

Analyzing

Block #95,178,679

18 transactions · 16 stateful · 2026-08-11 22:18:34 UTC

Parallelism

83/100

Blocked

31%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,178,679  ·  18 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0xbba9dcbb…e4c9

0x34b655…2a6f

6 touches
3 conflicts

0x367b69ad…33d8

0x34b655…2a6f

4 touches
1 conflict

0x367b69ad…33d9

0x34b655…2a6f

4 touches
1 conflict

0x3a5e95ba…806a

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0x8046ca3c…f094

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity