← previous blocknext block →recent activity

Analyzing

Block #96,369,805

24 transactions · 19 stateful · 2026-08-16 02:24:47 UTC

Parallelism

79/100

Blocked

37%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #96,369,805  ·  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

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xc922b09d…f650

0x34b655…2a6f

6 touches
3 conflicts

0xa6848351…2238

0x34b655…2a6f

6 touches
3 conflicts

0x2fdfa032…139c

0x34b655…2a6f

4 touches
1 conflict

0x3c7c65d0…0b52

0x34b655…2a6f

4 touches
1 conflict

0x57be321f…fecc

0x34b655…2a6f

4 touches
1 conflict

0x6f97afda…faec

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

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity