← previous blocknext block →recent activity

Analyzing

Block #96,640,142

22 transactions · 22 stateful · 2026-08-17 01:04:46 UTC

Parallelism

77/100

Blocked

32%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #96,640,142  ·  22 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

0x66d5e476…8a1f

0x34b655…2a6f

6 touches
3 conflicts

0x6bdb9869…7558

0x34b655…2a6f

6 touches
3 conflicts

0xf0d45ffd…89cf

0x34b655…2a6f

6 touches
3 conflicts

0x3a2b650f…f454

0x34b655…2a6f

4 touches
1 conflict

0x42e917f7…ed8c

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x6a764ba5…54b7

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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 0x66d5e476c0…268a1f

← previous block·next block →recent activity