← previous blocknext block →recent activity

Analyzing

Block #86,335,877

28 transactions · 22 stateful · 2026-07-08 04:27:02 UTC

Parallelism

89/100

Blocked

32%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,335,877  ·  28 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xf8d7f8b3…c32e

0xa6afd3…d132

5 touches
3 conflicts

0xf0863f1e…faae

0xd32edf…ff58

5 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x3359bed7…0867

0x065c9d…c394

4 touches
1 conflict

0x40e2d65d…2a35

0x3bd359…433a

4 touches
1 conflict

0xef65bff3…7c9d

0x2a68ba…90c5

4 touches
1 conflict

0x11b69a7e…334e

0xee8c0e…1242

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