← previous blocknext block →recent activity

Analyzing

Block #97,671,043

32 transactions · 29 stateful · 2026-08-20 16:25:08 UTC

Parallelism

66/100

Blocked

52%

Avg conflicts / tx

1.56

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #97,671,043  ·  32 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

18 touches
36 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x097382dd…d21d

0x065c9d…c394

9 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x5f77d607…2c84

0x065c9d…c394

6 touches
3 conflicts

0x3a3097d7…2ab6

0x1b6862…e19c

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

36 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity