← previous blocknext block →recent activity

Analyzing

Block #100,609,126

26 transactions · 20 stateful · 2026-08-31 00:09:36 UTC

Parallelism

85/100

Blocked

35%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,609,126  ·  26 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

0x889d5e90…929a

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…0000

0x354d92…66fb

4 touches
1 conflict

0x00000000…0001

0x354d92…66fb

4 touches
1 conflict

0x8a2f9a36…fb4a

0x354d92…66fb

4 touches
1 conflict

0x0c30eaf8…cc06

0x40c49f…2af0

4 touches
1 conflict

0x02f4f6e2…47c6

0x754704…b603

4 touches
1 conflict

0x0449d018…e334

0x754704…b603

4 touches
1 conflict

0x58a864a6…57e3

0x754704…b603

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 0x889d5e90c7…59929a

← previous block·next block →recent activity