← previous blocknext block →recent activity

Analyzing

Block #86,339,873

22 transactions · 19 stateful · 2026-07-08 04:53:43 UTC

Parallelism

77/100

Blocked

32%

Avg conflicts / tx

0.45

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,339,873  ·  22 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x3181bd2d…cf15

0xa6afd3…d132

4 touches
1 conflict

0xe5a9274d…78d7

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0xb88785d1…2309

0x40c49f…2af0

4 touches
1 conflict

0x112cf8ad…6e4f

0xa6afd3…d132

4 touches
1 conflict

0x0c366266…77e1

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 0xf2f76ab392…f3623e

← previous block·next block →recent activity