← previous blocknext block →recent activity

Analyzing

Block #85,991,913

35 transactions · 26 stateful · 2026-07-06 14:10:33 UTC

Parallelism

86/100

Blocked

27%

Avg conflicts / tx

0.31

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,991,913  ·  35 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

6 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0x57446c1b…bd83

0xd32edf…ff58

5 touches
3 conflicts

0xda8c1c92…2503

0x065c9d…c394

5 touches
3 conflicts

0xdf3881e7…211d

0x065c9d…c394

4 touches
1 conflict

0x01e7b865…6e6e

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x52e69143…95ad

0x065c9d…c394

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

← previous block·next block →recent activity