← previous blocknext block →recent activity

Analyzing

Block #97,732,280

16 transactions · 14 stateful · 2026-08-20 21:36:35 UTC

Parallelism

88/100

Blocked

21%

Avg conflicts / tx

0.31

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #97,732,280  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0xa2428b0b…9500

0x34b655…2a6f

4 touches
1 conflict

0x6a9e408e…3721

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xcf13e6ba…e2ff

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0007

0xc1570a…c91b

4 touches
1 conflict

0x8ff85b19…dde0

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

1 conflict on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity