← previous blocknext block →recent activity

Analyzing

Block #96,265,159

7 transactions · 7 stateful · 2026-08-15 17:38:28 UTC

Parallelism

57/100

Blocked

43%

Avg conflicts / tx

0.57

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #96,265,159  ·  7 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x6b17f7a0…af41

0x34b655…2a6f

6 touches
3 conflicts

0xcbe18c62…3a5c

0x34b655…2a6f

4 touches
1 conflict

0xcbe18c62…3a5d

0x34b655…2a6f

4 touches
1 conflict

0x6d1b72ee…6b78

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x1bd6ddeb…9a19

0x34b655…2a6f

4 touches
1 conflict

0x7dc9a515…1ee5

0x34b655…2a6f

3 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

2 touches
0 conflicts

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 0x6b17f7a0cf…37af41

← previous block·next block →recent activity