← previous blocknext block →recent activity

Analyzing

Block #96,293,616

13 transactions · 10 stateful · 2026-08-15 20:01:35 UTC

Parallelism

85/100

Blocked

30%

Avg conflicts / tx

0.23

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #96,293,616  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x633c5300…fd46

0x968279…9342

4 touches
1 conflict

0x633c5300…fd47

0x968279…9342

4 touches
1 conflict

0x633c5300…fd49

0x968279…9342

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x44331cd1…15b0

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x177211e2…1c2d

0x754704…b603

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: 0x96827978…f09342

1 conflict on slot 0x633c530018…3bfd46

← previous block·next block →recent activity