← previous blocknext block →recent activity

Analyzing

Block #100,630,292

19 transactions · 19 stateful · 2026-08-31 01:56:04 UTC

Parallelism

84/100

Blocked

32%

Avg conflicts / tx

0.58

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,630,292  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x1dedc384…ff57

0x851145…3f07

6 touches
3 conflicts

0x2ce5d13f…f8a9

0x851145…3f07

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xf1a14809…56fd

0x34ae4d…3fc5

4 touches
1 conflict

0x315e07b8…9823

0x34b655…2a6f

4 touches
1 conflict

0x5efd7300…d8a5

0x34b655…2a6f

4 touches
1 conflict

0x7e06d07b…36af

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 0x002fed350f…7379fa

← previous block·next block →recent activity