← previous blocknext block →recent activity

Analyzing

Block #85,931,946

25 transactions · 22 stateful · 2026-07-06 07:30:15 UTC

Parallelism

88/100

Blocked

32%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #85,931,946  ·  25 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

0x160f117d…8e90

0x065c9d…c394

6 touches
3 conflicts

0xb33ff823…1188

0x065c9d…c394

6 touches
3 conflicts

0xa20a130c…5d59

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x333ef238…6203

0x34b655…2a6f

4 touches
1 conflict

0x3439dfbc…0d03

0x34b655…2a6f

4 touches
1 conflict

0x52342825…6e5c

0x34b655…2a6f

4 touches
1 conflict

0x62341e2a…2d78

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 0x160f117d43…518e90

← previous block·next block →recent activity