← previous blocknext block →recent activity

Analyzing

Block #96,601,564

16 transactions · 16 stateful · 2026-08-16 21:50:44 UTC

Parallelism

69/100

Blocked

44%

Avg conflicts / tx

0.56

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #96,601,564  ·  16 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

0xb15e92da…72fe

0x34b655…2a6f

6 touches
3 conflicts

0x0bd95eb4…e562

0x34b655…2a6f

4 touches
1 conflict

0x0d488000…3831

0x34b655…2a6f

4 touches
1 conflict

0x2a1086da…dba7

0x34b655…2a6f

4 touches
1 conflict

0x31d88d27…7617

0x34b655…2a6f

4 touches
1 conflict

0x3b689fd2…629c

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7b42f6a7…f49c

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 0xb15e92da95…0b72fe

← previous block·next block →recent activity