← previous blocknext block →recent activity

Analyzing

Block #86,883,108

23 transactions · 21 stateful · 2026-07-10 17:26:31 UTC

Parallelism

78/100

Blocked

38%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,883,108  ·  23 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

0xd35bb5ac…3586

0x065c9d…c394

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x1c03f81f…b303

0x34b655…2a6f

4 touches
1 conflict

0x1c03f81f…b304

0x34b655…2a6f

4 touches
1 conflict

0x453f53a8…e541

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 0xd35bb5ac3f…003586

← previous block·next block →recent activity