← previous blocknext block →recent activity

Analyzing

Block #97,565,167

21 transactions · 18 stateful · 2026-08-20 07:24:25 UTC

Parallelism

81/100

Blocked

28%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,565,167  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x516e9b35…57e7

0x34b655…2a6f

6 touches
3 conflicts

0x399d1d29…f395

0x34b655…2a6f

4 touches
1 conflict

0x4709ec24…a6dd

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0007

0xc1570a…c91b

4 touches
1 conflict

0x1c150953…c2d9

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity