← previous blocknext block →recent activity

Analyzing

Block #108,619,554

41 transactions · 32 stateful · 2026-09-28 01:25:20 UTC

Parallelism

81/100

Blocked

53%

Avg conflicts / tx

1.29

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #108,619,554  ·  41 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xf3d7a307…4d63

0x065c9d…c394

16 touches
28 conflicts

0x00000000…003d

0x065c9d…c394

16 touches
28 conflicts

0xba38536d…2b7d

0x065c9d…c394

14 touches
21 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

14 touches
21 conflicts

0xa17ec269…7cdd

0x34ae4d…3fc5

12 touches
15 conflicts

0xa605468c…1bfc

0x34ae4d…3fc5

12 touches
15 conflicts

0xc8525006…2b45

0x34ae4d…3fc5

12 touches
15 conflicts

0xb686e6f5…f6d1

0xc8689a…ee79

12 touches
15 conflicts

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: Market-MON/USDC

28 conflicts on slot 0xf3d7a307cc…f14d63

← previous block·next block →recent activity