← previous blocknext block →recent activity

Analyzing

Block #108,873,579

21 transactions · 19 stateful · 2026-09-28 22:47:07 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.86

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #108,873,579  ·  21 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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xf3d7a307…4d63

0x065c9d…c394

8 touches
6 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x237ae0f2…97d8

0x34b655…2a6f

4 touches
1 conflict

0x4c29ecd5…58b6

0x34b655…2a6f

4 touches
1 conflict

0x63435b04…27de

0x34b655…2a6f

4 touches
1 conflict

0x689be8aa…54e7

0x34b655…2a6f

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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity