← previous blocknext block →recent activity

Analyzing

Block #100,849,077

25 transactions · 24 stateful · 2026-08-31 20:17:03 UTC

Parallelism

72/100

Blocked

46%

Avg conflicts / tx

1.16

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,849,077  ·  25 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

0x0b02e6d5…c54d

0x40c49f…2af0

10 touches
10 conflicts

0x2b54cadb…4425

0xd18b7e…414b

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002b

0x1b6862…e19c

6 touches
3 conflicts

0xd53220ed…4737

0x1b6862…e19c

6 touches
3 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