← previous blocknext block →recent activity

Analyzing

Block #86,753,294

17 transactions · 15 stateful · 2026-07-10 02:58:52 UTC

Parallelism

82/100

Blocked

47%

Avg conflicts / tx

0.53

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,753,294  ·  17 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

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x8a35acfb…d1a9

0xb1dbf0…c0d3

6 touches
3 conflicts

0x8a35acfb…d1a8

0xb1dbf0…c0d3

6 touches
3 conflicts

0x793aa64d…b09d

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0x975922f7…be0a

0x34b655…2a6f

4 touches
1 conflict

0xbc4e7b49…3d2d

0x34b655…2a6f

4 touches
1 conflict

0xc5074ade…2560

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: MarginAccount

3 conflicts on slot 0x13a54fa2d3…a35ae3

← previous block·next block →recent activity