← previous blocknext block →recent activity

Analyzing

Block #100,862,691

20 transactions · 14 stateful · 2026-08-31 21:25:32 UTC

Parallelism

85/100

Blocked

43%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,862,691  ·  20 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

0x6518075e…2b17

0x2a68ba…90c5

6 touches
3 conflicts

0x247491b7…ef54

0x40c49f…2af0

6 touches
3 conflicts

0x2b54cadb…4425

0xd18b7e…414b

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0x2f358e74…1022

0x34b655…2a6f

4 touches
1 conflict

0x33000c0a…82c3

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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 0x6518075e89…5f2b17

← previous block·next block →recent activity