← previous blocknext block →recent activity

Analyzing

Block #82,693,789

23 transactions · 22 stateful · 2026-06-21 07:31:39 UTC

Parallelism

57/100

Blocked

64%

Avg conflicts / tx

1.57

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #82,693,789  ·  23 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

10 touches
10 conflicts

0x8a751d7a…247c

0xa6afd3…d132

10 touches
10 conflicts

0x00000000…003d

0xa6afd3…d132

10 touches
10 conflicts

0x9fb55ee7…8ecc

0xa6afd3…d132

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xb3c96942…f0fc

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x76d1e78d…7877

0x40c49f…2af0

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

10 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity