← previous blocknext block →recent activity

Analyzing

Block #100,858,677

27 transactions · 21 stateful · 2026-08-31 21:05:20 UTC

Parallelism

74/100

Blocked

57%

Avg conflicts / tx

1.07

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,858,677  ·  27 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

0xaad6be10…0801

0x2a68ba…90c5

14 touches
21 conflicts

0x3e1e8e54…9c83

0x2a68ba…90c5

8 touches
6 conflicts

0x46279ae7…20dd

0x34ae4d…3fc5

8 touches
6 conflicts

0x6eff310a…c34c

0x34ae4d…3fc5

8 touches
6 conflicts

0xb55a7cbc…68f5

0x34ae4d…3fc5

8 touches
6 conflicts

0xdeed550b…338b

0x34ae4d…3fc5

8 touches
6 conflicts

0xe49b1b9b…0be1

0x34ae4d…3fc5

8 touches
6 conflicts

0x00000000…003d

0x40c49f…2af0

8 touches
6 conflicts

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

21 conflicts on slot 0xaad6be10ae…2c0801

← previous block·next block →recent activity