← previous blocknext block →recent activity

Analyzing

Block #108,671,809

23 transactions · 21 stateful · 2026-09-28 05:48:31 UTC

Parallelism

78/100

Blocked

38%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #108,671,809  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x2d9ecc9e…5a04

0x851145…3f07

4 touches
1 conflict

0x4f5d8f7e…6f56

0x851145…3f07

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

← previous block·next block →recent activity