← previous blocknext block →recent activity

Analyzing

Block #97,551,968

32 transactions · 20 stateful · 2026-08-20 06:16:53 UTC

Parallelism

91/100

Blocked

30%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #97,551,968  ·  32 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x886db264…846e

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x98d1f315…caa4

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0029

0x1b6862…e19c

4 touches
1 conflict

0x0a6cb118…4ca4

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity