← previous blocknext block →recent activity

Analyzing

Block #93,669,708

20 transactions · 20 stateful · 2026-08-06 15:30:43 UTC

Parallelism

85/100

Blocked

35%

Avg conflicts / tx

0.55

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #93,669,708  ·  20 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

0x7cd7675d…a0b7

0x065c9d…c394

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x20d57805…d59a

0x065c9d…c394

4 touches
2 conflicts

0xfb874a6c…caa0

0x34b655…2a6f

4 touches
1 conflict

0x4526453d…cac2

0x065c9d…c394

4 touches
1 conflict

0xbbeac3b7…c14b

0x34b655…2a6f

4 touches
1 conflict

0xe7aef4d2…32cb

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 0x7cd7675dc0…d0a0b7

← previous block·next block →recent activity