← previous blocknext block →recent activity

Analyzing

Block #85,893,607

19 transactions · 17 stateful · 2026-07-06 03:14:46 UTC

Parallelism

79/100

Blocked

41%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,893,607  ·  19 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

0x160f117d…8e90

0x065c9d…c394

8 touches
6 conflicts

0xb33ff823…1188

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xb124726d…afb5

0x065c9d…c394

5 touches
3 conflicts

0xdeb91b9b…baaf

0x065c9d…c394

5 touches
3 conflicts

0xb1f0701d…4f4a

0xc8689a…ee79

4 touches
1 conflict

0x00000000…0002

0x04fdea…47d7

4 touches
1 conflict

0x1d290f8b…2ad7

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

6 conflicts on slot 0x160f117d43…518e90

← previous block·next block →recent activity