← previous blocknext block →recent activity

Analyzing

Block #86,493,330

22 transactions · 18 stateful · 2026-07-08 21:59:17 UTC

Parallelism

86/100

Blocked

33%

Avg conflicts / tx

0.41

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,493,330  ·  22 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

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x922c7ebd…6600

0xc8689a…ee79

4 touches
1 conflict

0x6827c800…a1a1

0x34b655…2a6f

4 touches
1 conflict

0x75959b84…9bda

0x34b655…2a6f

4 touches
1 conflict

0x9966da31…0d0f

0x34b655…2a6f

4 touches
1 conflict

0xb78c746a…de83

0x34b655…2a6f

4 touches
1 conflict

0xcfa965cc…6fcf

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