← previous blocknext block →recent activity

Analyzing

Block #96,022,917

19 transactions · 17 stateful · 2026-08-14 21:20:00 UTC

Parallelism

68/100

Blocked

47%

Avg conflicts / tx

0.63

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #96,022,917  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf8c43727…4760

0x34b655…2a6f

8 touches
6 conflicts

0x56153262…21ce

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x21898044…a071

0x065c9d…c394

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x0f6aef87…8137

0x34b655…2a6f

4 touches
1 conflict

0x3f4f9f22…8ad7

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

6 conflicts on slot 0xf8c43727d1…3f4760

← previous block·next block →recent activity