← previous blocknext block →recent activity

Analyzing

Block #86,315,511

25 transactions · 20 stateful · 2026-07-08 02:11:00 UTC

Parallelism

88/100

Blocked

30%

Avg conflicts / tx

0.32

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,315,511  ·  25 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xa57576bb…e01f

0x34b655…2a6f

4 touches
1 conflict

0xaf498679…7732

0x34b655…2a6f

4 touches
1 conflict

0xfc578b53…9b1f

0xa6afd3…d132

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x112cf8ad…6e4f

0xa6afd3…d132

4 touches
1 conflict

0x1d9867ad…6d9a

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

← previous block·next block →recent activity