← previous blocknext block →recent activity

Analyzing

Block #106,039,029

16 transactions · 16 stateful · 2026-09-19 00:53:29 UTC

Parallelism

75/100

Blocked

56%

Avg conflicts / tx

1.06

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #106,039,029  ·  16 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

0x95523e2a…4c01

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0x94dabb65…43a3

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x03d037d1…564d

0x34b655…2a6f

4 touches
1 conflict

0x085df2c1…305a

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

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

6 conflicts on slot 0x95523e2aaf…734c01

← previous block·next block →recent activity