← previous blocknext block →recent activity

Analyzing

Block #97,989,929

19 transactions · 18 stateful · 2026-08-21 19:27:01 UTC

Parallelism

79/100

Blocked

28%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,989,929  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xcaa5e459…c7eb

0x34b655…2a6f

6 touches
3 conflicts

0x25950a46…ced6

0xa6afd3…d132

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x00000000…0007

0x340143…768f

4 touches
1 conflict

0x178fe051…465a

0x34b655…2a6f

4 touches
1 conflict

0x26a87710…7301

0x34b655…2a6f

4 touches
1 conflict

0x3ccb7992…8653

0x34b655…2a6f

4 touches
1 conflict

0x3e49348b…9445

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 0xcaa5e45985…ccc7eb

← previous block·next block →recent activity