← previous blocknext block →recent activity

Analyzing

Block #86,611,159

19 transactions · 15 stateful · 2026-07-09 11:08:19 UTC

Parallelism

84/100

Blocked

47%

Avg conflicts / tx

0.53

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,611,159  ·  19 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

0x489cb750…7069

0x065c9d…c394

6 touches
3 conflicts

0x8a35acfb…d1aa

0xb1dbf0…c0d3

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xd35bb5ac…3586

0x065c9d…c394

6 touches
3 conflicts

0x8a35acfb…d1a9

0xb1dbf0…c0d3

6 touches
3 conflicts

0x1e451306…7993

0xb1dbf0…c0d3

4 touches
1 conflict

0x6a248bdc…3c1b

0xb1dbf0…c0d3

4 touches
1 conflict

0xb07a0849…3b62

0xb1dbf0…c0d3

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 0x489cb75090…f57069

← previous block·next block →recent activity