← previous blocknext block →recent activity

Analyzing

Block #96,603,738

18 transactions · 18 stateful · 2026-08-16 22:01:40 UTC

Parallelism

78/100

Blocked

39%

Avg conflicts / tx

0.61

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #96,603,738  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x733a5000…6e67

0x34b655…2a6f

6 touches
3 conflicts

0xb762713c…bcd7

0x34b655…2a6f

6 touches
3 conflicts

0x840d3ab7…c8c4

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4e697adf…0ac0

0x34b655…2a6f

4 touches
1 conflict

0x5b7559b6…6072

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0xa0d16e22…ba49

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 0x733a5000e7…e16e67

← previous block·next block →recent activity