← previous blocknext block →recent activity

Analyzing

Block #96,031,569

17 transactions · 14 stateful · 2026-08-14 22:03:31 UTC

Parallelism

71/100

Blocked

57%

Avg conflicts / tx

0.82

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #96,031,569  ·  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

0x6517c94f…361d

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x7b55198a…b946

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x2130a548…c1de

0x34b655…2a6f

6 touches
3 conflicts

0x3d93ad2c…e747

0x34b655…2a6f

6 touches
3 conflicts

0x6ff63ad4…2a08

0x34b655…2a6f

4 touches
1 conflict

0x7c0bdc54…9dde

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

10 conflicts on slot 0x6517c94f08…34361d

← previous block·next block →recent activity