← previous blocknext block →recent activity

Analyzing

Block #97,370,578

25 transactions · 19 stateful · 2026-08-19 14:40:59 UTC

Parallelism

56/100

Blocked

58%

Avg conflicts / tx

1.8

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #97,370,578  ·  25 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xc824469a…6425

0x34b655…2a6f

18 touches
36 conflicts

0x482471ad…122f

0x34b655…2a6f

18 touches
36 conflicts

0x0bcbbcad…fc9c

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x4f3a6b4a…3819

0x34b655…2a6f

8 touches
6 conflicts

0xb409e204…89ac

0x34b655…2a6f

8 touches
6 conflicts

0x8b5fdd23…afe5

0x34b655…2a6f

8 touches
6 conflicts

0x1e817e5d…c381

0x34b655…2a6f

7 touches
6 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

36 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity