← previous blocknext block →recent activity

Analyzing

Block #102,476,967

24 transactions · 23 stateful · 2026-09-06 13:08:53 UTC

Parallelism

83/100

Blocked

26%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,476,967  ·  24 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x21adef83…f2b7

0x34b655…2a6f

6 touches
3 conflicts

0x045532dd…4b7d

0x34b655…2a6f

4 touches
1 conflict

0x2e1f5171…ad2d

0x34b655…2a6f

4 touches
1 conflict

0x3a02c642…17f1

0x34b655…2a6f

4 touches
1 conflict

0x56a284d9…32e4

0x34b655…2a6f

4 touches
1 conflict

0x616cf672…6983

0x34b655…2a6f

4 touches
1 conflict

0x66d0c4a4…add3

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