← previous blocknext block →recent activity

Analyzing

Block #97,612,789

16 transactions · 16 stateful · 2026-08-20 11:25:35 UTC

Parallelism

56/100

Blocked

50%

Avg conflicts / tx

1.38

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #97,612,789  ·  16 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x40ac662f…df77

0x34b655…2a6f

12 touches
15 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x886db264…846e

0x34b655…2a6f

6 touches
3 conflicts

0x57823377…8ce3

0x34b655…2a6f

4 touches
1 conflict

0x680fdd59…e84d

0x34b655…2a6f

4 touches
1 conflict

0x8cd2695f…b6c2

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

15 conflicts on slot 0x40ac662f45…43df77

← previous block·next block →recent activity