← previous blocknext block →recent activity

Analyzing

Block #85,757,375

22 transactions · 17 stateful · 2026-07-05 12:07:28 UTC

Parallelism

86/100

Blocked

35%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #85,757,375  ·  22 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

0x00000000…0002

0x04fdea…47d7

6 touches
3 conflicts

0x2886e2bc…6ab8

0x065c9d…c394

4 touches
1 conflict

0x731e6d82…2883

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x31cc0daa…8583

0x065c9d…c394

3 touches
1 conflict

0x6de83484…1d83

0x065c9d…c394

3 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