← previous blocknext block →recent activity

Analyzing

Block #96,695,236

23 transactions · 17 stateful · 2026-08-17 05:41:51 UTC

Parallelism

78/100

Blocked

41%

Avg conflicts / tx

0.43

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #96,695,236  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x8590b692…b267

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x61b9ae60…baa6

0xd32edf…ff58

5 touches
3 conflicts

0x620b761c…270e

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xc61d8a1d…18fd

0x34b655…2a6f

4 touches
1 conflict

0xcd176877…2c75

0x34b655…2a6f

4 touches
1 conflict

0xdb392027…0308

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 0x8590b69238…6ab267

← previous block·next block →recent activity