← previous blocknext block →recent activity

Analyzing

Block #97,530,639

18 transactions · 16 stateful · 2026-08-20 04:29:18 UTC

Parallelism

83/100

Blocked

38%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #97,530,639  ·  18 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

0x1dc86774…166a

0x34b655…2a6f

6 touches
3 conflicts

0x2685bd42…9f0d

0x34b655…2a6f

4 touches
1 conflict

0x2dcc0868…26bf

0x34b655…2a6f

4 touches
1 conflict

0x609a25a3…8785

0x34b655…2a6f

4 touches
1 conflict

0x6c60fbcf…8744

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7b4b55ac…20ff

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

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 0x1dc86774a8…36166a

← previous block·next block →recent activity