← previous blocknext block →recent activity

Analyzing

Block #97,396,256

20 transactions · 18 stateful · 2026-08-19 17:11:11 UTC

Parallelism

80/100

Blocked

39%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,396,256  ·  20 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

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xec431e8f…8c4d

0x34b655…2a6f

4 touches
1 conflict

0x160f117d…8e90

0x065c9d…c394

4 touches
1 conflict

0x00000000…0007

0xc1570a…c91b

4 touches
1 conflict

0x1bfd6618…7d78

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

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: Kuru Exchange: MarginAccount

3 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity