← previous blocknext block →recent activity

Analyzing

Block #97,478,668

34 transactions · 29 stateful · 2026-08-20 00:07:51 UTC

Parallelism

79/100

Blocked

48%

Avg conflicts / tx

1.21

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #97,478,668  ·  34 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

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x482471ad…122f

0x34b655…2a6f

14 touches
21 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x11258774…9892

0x2a68ba…90c5

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x1dc86774…166a

0x34b655…2a6f

6 touches
3 conflicts

0x2efca342…cd6d

0x34b655…2a6f

6 touches
3 conflicts

0x59a84baf…4dfa

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