← previous blocknext block →recent activity

Analyzing

Block #97,356,877

23 transactions · 21 stateful · 2026-08-19 13:30:28 UTC

Parallelism

78/100

Blocked

38%

Avg conflicts / tx

0.74

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,356,877  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0xd6bd849a…5597

0x2a68ba…90c5

8 touches
6 conflicts

0x10d80fee…dbda

0x2b46c0…1669

8 touches
6 conflicts

0x40970e69…da50

0x2b46c0…1669

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

8 touches
6 conflicts

0x8cf3d245…1d0d

0x2b46c0…1669

8 touches
6 conflicts

0xdb067026…9eb8

0x2b46c0…1669

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 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

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity