← previous blocknext block →recent activity

Analyzing

Block #108,653,508

16 transactions · 14 stateful · 2026-09-28 04:16:20 UTC

Parallelism

88/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #108,653,508  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x443a3e47…f4a4

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x05006bd2…56ea

0x508254…98bd

4 touches
1 conflict

0x3a663e9a…a9c5

0x508254…98bd

4 touches
1 conflict

0x3a663e9a…a9c6

0x508254…98bd

4 touches
1 conflict

0x3a663e9a…a9c8

0x508254…98bd

4 touches
1 conflict

0x3a663e9a…a9c9

0x508254…98bd

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity