← previous blocknext block →recent activity

Analyzing

Block #96,795,595

24 transactions · 19 stateful · 2026-08-17 14:06:37 UTC

Parallelism

79/100

Blocked

37%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #96,795,595  ·  24 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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc5a1b2fe…5369

0x34b655…2a6f

6 touches
3 conflicts

0xacd1b162…bee6

0x34b655…2a6f

6 touches
3 conflicts

0xcc4a4bb2…395d

0x34b655…2a6f

6 touches
3 conflicts

0xacb9dcc7…19bc

0x34b655…2a6f

4 touches
1 conflict

0x42041fec…bd86

0x754704…b603

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

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 0xc824469a90…af6425

← previous block·next block →recent activity