← previous blocknext block →recent activity

Analyzing

Block #95,976,555

17 transactions · 17 stateful · 2026-08-14 17:26:41 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.88

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,976,555  ·  17 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x1cc1ec8e…be2f

0x34b655…2a6f

8 touches
6 conflicts

0x272e5bd6…252d

0x34b655…2a6f

6 touches
3 conflicts

0x34ac5036…bedf

0x34b655…2a6f

6 touches
3 conflicts

0xa0d3a786…91d9

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xfc371f5e…0955

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x1a5d321d…a474

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

6 conflicts on slot 0x1cc1ec8e36…6abe2f

← previous block·next block →recent activity