← previous blocknext block →recent activity

Analyzing

Block #100,978,623

25 transactions · 23 stateful · 2026-09-01 07:08:40 UTC

Parallelism

76/100

Blocked

39%

Avg conflicts / tx

0.88

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #100,978,623  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xb87af72a…aef6

0x2a68ba…90c5

12 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x078bff01…524f

0x065c9d…c394

7 touches
6 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xb686e6f5…f6d1

0xc8689a…ee79

4 touches
1 conflict

0x443a3e47…f4a4

0x065c9d…c394

4 touches
1 conflict

0x6f7f2b71…50bc

0x065c9d…c394

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

15 conflicts on slot 0xb87af72ae5…0baef6

← previous block·next block →recent activity