← previous blocknext block →recent activity

Analyzing

Block #97,195,678

22 transactions · 18 stateful · 2026-08-18 23:52:07 UTC

Parallelism

68/100

Blocked

50%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #97,195,678  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x002fed35…79fa

0x2a68ba…90c5

10 touches
10 conflicts

0x53417337…4e3a

0xa6afd3…d132

9 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x11b69a7e…334e

0xee8c0e…1242

8 touches
6 conflicts

0x9f27e2e6…ea8e

0xd32edf…ff58

7 touches
6 conflicts

0xa86351b8…2c5a

0x34b655…2a6f

6 touches
3 conflicts

0x8d47c9a4…f11c

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

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

10 conflicts on slot 0x002fed350f…7379fa

← previous block·next block →recent activity