← previous blocknext block →recent activity

Analyzing

Block #97,395,951

37 transactions · 31 stateful · 2026-08-19 17:09:38 UTC

Parallelism

78/100

Blocked

77%

Avg conflicts / tx

1.73

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #97,395,951  ·  37 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

0xec7d120d…7084

0x34b655…2a6f

14 touches
21 conflicts

0x00000000…0002

0x103de0…bb55

12 touches
15 conflicts

0xd7a3d42d…e766

0x40c49f…2af0

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

8 touches
6 conflicts

0x221a6ee3…2a3c

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x40c49f…2af0

8 touches
6 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

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 0xec7d120df9…5d7084

← previous block·next block →recent activity