← previous blocknext block →recent activity

Analyzing

Block #96,527,326

14 transactions · 10 stateful · 2026-08-16 15:37:20 UTC

Parallelism

79/100

Blocked

30%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #96,527,326  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x827557c1…a6be

0x34b655…2a6f

4 touches
1 conflict

0x18d306ad…d8f4

0x34b655…2a6f

2 touches
0 conflicts

0x3e3f27ce…580c

0x34b655…2a6f

2 touches
0 conflicts

0x46483cb1…e7ca

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity