← previous blocknext block →recent activity

Analyzing

Block #82,707,603

21 transactions · 17 stateful · 2026-06-21 09:03:45 UTC

Parallelism

67/100

Blocked

53%

Avg conflicts / tx

1.05

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #82,707,603  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xf9f48af5…4205

0xa6afd3…d132

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0xb3572c95…9c4a

0x2a68ba…90c5

8 touches
6 conflicts

0x26470289…bb21

0xa6afd3…d132

4 touches
1 conflict

0x5d46e6a0…5ed9

0x40c49f…2af0

4 touches
1 conflict

0x5d431ee2…4319

0x40c49f…2af0

4 touches
1 conflict

0x22e0cc1d…ad04

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