← previous blocknext block →recent activity

Analyzing

Block #102,741,621

23 transactions · 22 stateful · 2026-09-07 11:26:13 UTC

Parallelism

87/100

Blocked

27%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,741,621  ·  23 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xcc4f1f14…aa5f

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0002

0xf5b5f7…6d70

4 touches
1 conflict

0x4188cc5f…2d2e

0x34b655…2a6f

4 touches
1 conflict

0x42e5184f…4e8b

0x34b655…2a6f

4 touches
1 conflict

0x6ae4f36b…5ce4

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641f

0x34b655…2a6f

4 touches
1 conflict

0xfd9bfada…b65b

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity