← previous blocknext block →recent activity

Analyzing

Block #85,761,540

20 transactions · 18 stateful · 2026-07-05 12:35:09 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.85

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,761,540  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x92687844…6382

0x065c9d…c394

4 touches
1 conflict

0xd99b3b64…1c95

0x34b655…2a6f

4 touches
1 conflict

0x2886e2bc…6ab8

0x065c9d…c394

4 touches
1 conflict

0x731e6d82…2883

0x065c9d…c394

4 touches
1 conflict

0x8df044e3…b49f

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 0x0000000000…00003d

← previous block·next block →recent activity