← previous blocknext block →recent activity

Analyzing

Block #97,357,347

24 transactions · 20 stateful · 2026-08-19 13:32:55 UTC

Parallelism

63/100

Blocked

60%

Avg conflicts / tx

1.83

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #97,357,347  ·  24 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x482471ad…122f

0x34b655…2a6f

18 touches
36 conflicts

0xc824469a…6425

0x34b655…2a6f

18 touches
36 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xbb322930…ace5

0x34b655…2a6f

8 touches
6 conflicts

0xb409e204…89ac

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…004c

0x80c745…7210

6 touches
3 conflicts

0x4e58f1d6…2fca

0x34b655…2a6f

6 touches
3 conflicts

0xb527b877…3047

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

36 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity