← previous blocknext block →recent activity

Analyzing

Block #96,150,009

21 transactions · 17 stateful · 2026-08-15 07:59:19 UTC

Parallelism

90/100

Blocked

29%

Avg conflicts / tx

0.24

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #96,150,009  ·  21 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x9b2d3bee…8eeb

0x34b655…2a6f

4 touches
1 conflict

0x9b2d3bee…8eec

0x34b655…2a6f

4 touches
1 conflict

0xea1b8c07…b969

0x34b655…2a6f

4 touches
1 conflict

0xfb84f2e3…6d5a

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x6d1b72ee…6b78

0x34b655…2a6f

4 touches
1 conflict

0x7d3e3b93…b8eb

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

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

1 conflict on slot 0x9b2d3bee9d…d68eeb

← previous block·next block →recent activity