← previous blocknext block →recent activity

Analyzing

Block #97,826,205

18 transactions · 18 stateful · 2026-08-21 05:30:38 UTC

Parallelism

72/100

Blocked

39%

Avg conflicts / tx

1.22

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,826,205  ·  18 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

0xd597209e…9800

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xcf10b6c3…c186

0x34b655…2a6f

8 touches
6 conflicts

0x594b0c08…cd24

0x34b655…2a6f

6 touches
3 conflicts

0xe38f7c29…72fc

0x34b655…2a6f

6 touches
3 conflicts

0xcb21158b…f18d

0x34b655…2a6f

6 touches
3 conflicts

0x451e482b…7e7d

0x34b655…2a6f

6 touches
3 conflicts

0xc027c9a1…7795

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

6 conflicts on slot 0xd597209e54…809800

← previous block·next block →recent activity