← previous blocknext block →recent activity

Analyzing

Block #85,796,886

20 transactions · 17 stateful · 2026-07-05 16:30:33 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,796,886  ·  20 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

0x13a54fa2…5ae3

0x2a68ba…90c5

8 touches
6 conflicts

0xb4c35fcd…43ae

0xa6afd3…d132

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0xdf708ee7…1fcf

0xc8689a…ee79

6 touches
3 conflicts

0xef65bff3…7c9d

0x2a68ba…90c5

6 touches
3 conflicts

0x0a6f5e37…6c3c

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x40970e69…da50

0x69df8a…6292

6 touches
3 conflicts

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 0x13a54fa2d3…a35ae3

← previous block·next block →recent activity