← previous blocknext block →recent activity

Analyzing

Block #82,328,563

21 transactions · 19 stateful · 2026-06-19 14:51:12 UTC

Parallelism

81/100

Blocked

37%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #82,328,563  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x66c5e348…51d0

0xa6afd3…d132

4 touches
1 conflict

0x793aa64d…b09d

0x34b655…2a6f

4 touches
1 conflict

0x9139252b…d3b5

0x34b655…2a6f

4 touches
1 conflict

0xb3c96942…f0fc

0x34b655…2a6f

4 touches
1 conflict

0xd99b3b64…1c95

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

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