← previous blocknext block →recent activity

Analyzing

Block #97,567,618

18 transactions · 17 stateful · 2026-08-20 07:36:54 UTC

Parallelism

67/100

Blocked

41%

Avg conflicts / tx

0.89

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #97,567,618  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x8d989c17…e984

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x18e86f02…fa98

0x34b655…2a6f

6 touches
3 conflicts

0x7aad02c6…b979

0x34b655…2a6f

4 touches
1 conflict

0x7b42f6a7…f49c

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity