← previous blocknext block →recent activity

Analyzing

Block #85,959,883

24 transactions · 20 stateful · 2026-07-06 10:36:35 UTC

Parallelism

83/100

Blocked

30%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,959,883  ·  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

0xd35bb5ac…3586

0x065c9d…c394

4 touches
1 conflict

0xa4f80979…4d71

0x065c9d…c394

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xec7d120d…7084

0x34b655…2a6f

4 touches
1 conflict

0x6e569a4f…7e8d

0x065c9d…c394

4 touches
1 conflict

0xd99b3b64…1c95

0x34b655…2a6f

4 touches
1 conflict

0xf6fa6646…cb3c

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