← previous blocknext block →recent activity

Analyzing

Block #100,856,743

27 transactions · 19 stateful · 2026-08-31 20:55:37 UTC

Parallelism

85/100

Blocked

32%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,856,743  ·  27 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x6518075e…2b17

0x2a68ba…90c5

8 touches
6 conflicts

0x2b54cadb…4425

0xd18b7e…414b

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x9fcae06e…5e48

0x40c49f…2af0

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0xaba6578d…bd48

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

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

6 conflicts on slot 0x6518075e89…5f2b17

← previous block·next block →recent activity