← previous blocknext block →recent activity

Analyzing

Block #96,022,794

17 transactions · 15 stateful · 2026-08-14 21:19:23 UTC

Parallelism

71/100

Blocked

53%

Avg conflicts / tx

0.53

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #96,022,794  ·  17 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

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xbb97db90…4c93

0xc8689a…ee79

4 touches
1 conflict

0xd0cd3305…f212

0x34b655…2a6f

4 touches
1 conflict

0xd6113c0f…0a4b

0x34b655…2a6f

4 touches
1 conflict

0xf5ea108a…dbf6

0x34b655…2a6f

4 touches
1 conflict

0x3464bbc5…a323

0xa6afd3…d132

4 touches
1 conflict

0xb3572c95…9c4a

0x2a68ba…90c5

4 touches
1 conflict

0x0f6aef87…8137

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 0xac2a02739b…81721b

← previous block·next block →recent activity