← previous blocknext block →recent activity

Analyzing

Block #96,299,068

18 transactions · 18 stateful · 2026-08-15 20:29:01 UTC

Parallelism

89/100

Blocked

11%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #96,299,068  ·  18 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

0x0be747d5…22e1

0x34b655…2a6f

4 touches
1 conflict

0x39bd1fab…a39c

0x34b655…2a6f

4 touches
1 conflict

0x4564a497…99e5

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xa46242d8…c0a8

0x34b655…2a6f

4 touches
1 conflict

0xe72b7c43…e5ed

0x34b655…2a6f

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

1 conflict on slot 0x0be747d5f3…e922e1

← previous block·next block →recent activity