← previous blocknext block →recent activity

Analyzing

Block #108,576,729

25 transactions · 24 stateful · 2026-09-27 21:49:43 UTC

Parallelism

84/100

Blocked

25%

Avg conflicts / tx

0.32

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #108,576,729  ·  25 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

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x3a663e9a…a9cb

0x508254…98bd

4 touches
1 conflict

0x3a663e9a…a9d6

0x508254…98bd

4 touches
1 conflict

0x3a663e9a…a9dc

0x508254…98bd

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6f

0x188d58…ea8e

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 0xaad6be10ae…2c0801

← previous block·next block →recent activity