← previous blocknext block →recent activity

Analyzing

Block #96,277,766

23 transactions · 19 stateful · 2026-08-15 18:41:53 UTC

Parallelism

83/100

Blocked

37%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #96,277,766  ·  23 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

0x34a1ee7e…fb20

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x9ff176a9…152e

0x065c9d…c394

6 touches
3 conflicts

0x992fec28…420d

0x34b655…2a6f

6 touches
3 conflicts

0x2e7a0c1d…caaf

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x524f0872…0d12

0x34b655…2a6f

4 touches
1 conflict

0x81da6711…3869

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 0x34a1ee7e95…7cfb20

← previous block·next block →recent activity