← previous blocknext block →recent activity

Analyzing

Block #85,986,327

25 transactions · 17 stateful · 2026-07-06 13:33:12 UTC

Parallelism

80/100

Blocked

41%

Avg conflicts / tx

0.56

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,986,327  ·  25 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

8 touches
6 conflicts

0xb43dc900…22f2

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0xd99b3b64…1c95

0x34b655…2a6f

4 touches
1 conflict

0x61684cf2…e923

0x34b655…2a6f

4 touches
1 conflict

0x7e8ebc95…aded

0x34b655…2a6f

4 touches
1 conflict

0x9495bffc…46e6

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

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity