← previous blocknext block →recent activity

Analyzing

Block #96,825,639

20 transactions · 19 stateful · 2026-08-17 16:37:45 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #96,825,639  ·  20 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

0xac3e4969…39e9

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xf9e23360…8ef7

0x34b655…2a6f

8 touches
6 conflicts

0xfc24540b…6463

0x34b655…2a6f

6 touches
3 conflicts

0x387ada6b…994f

0x34b655…2a6f

6 touches
3 conflicts

0x79de8ff8…0443

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 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

6 conflicts on slot 0xac3e4969cf…1739e9

← previous block·next block →recent activity