← previous blocknext block →recent activity

Analyzing

Block #97,514,526

23 transactions · 20 stateful · 2026-08-20 03:08:14 UTC

Parallelism

65/100

Blocked

45%

Avg conflicts / tx

1.22

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #97,514,526  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

14 touches
21 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

12 touches
15 conflicts

0xca401ec1…58f8

0x34b655…2a6f

10 touches
10 conflicts

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0x2de76221…561d

0x34b655…2a6f

6 touches
4 conflicts

0x948836ff…59ab

0x34b655…2a6f

6 touches
4 conflicts

0x478fa423…1a74

0x34b655…2a6f

6 touches
3 conflicts

0xf346808d…6ad4

0x34b655…2a6f

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

21 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity