← previous blocknext block →recent activity

Analyzing

Block #85,985,798

25 transactions · 15 stateful · 2026-07-06 13:29:39 UTC

Parallelism

80/100

Blocked

47%

Avg conflicts / tx

0.4

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,985,798  ·  25 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

0xa4f80979…4d71

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x18efc396…eaf0

0xd32edf…ff58

5 touches
3 conflicts

0x6637e421…af93

0x34b655…2a6f

4 touches
1 conflict

0xb4e7b3b3…a0e4

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xc948dbdc…199a

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 0xa4f8097941…fd4d71

← previous block·next block →recent activity