← previous blocknext block →recent activity

Analyzing

Block #85,898,239

26 transactions · 17 stateful · 2026-07-06 03:45:38 UTC

Parallelism

85/100

Blocked

41%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,898,239  ·  26 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

8 touches
6 conflicts

0x59dccbd8…2bf6

0x34b655…2a6f

6 touches
3 conflicts

0xa4f80979…4d71

0x065c9d…c394

6 touches
3 conflicts

0xb33ff823…1188

0x065c9d…c394

6 touches
3 conflicts

0x6f20119c…ea72

0x065c9d…c394

4 touches
1 conflict

0xc08d4b61…1299

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

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