← previous blocknext block →recent activity

Analyzing

Block #100,923,643

21 transactions · 17 stateful · 2026-09-01 02:32:07 UTC

Parallelism

86/100

Blocked

35%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,923,643  ·  21 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

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0x2ce5d13f…f8a9

0x851145…3f07

4 touches
1 conflict

0xc20bd100…8b0e

0x34ae4d…3fc5

4 touches
1 conflict

0x9dc04c30…bc97

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

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 0xaad6be10ae…2c0801

← previous block·next block →recent activity