← previous blocknext block →recent activity

Analyzing

Block #82,022,193

21 transactions · 18 stateful · 2026-06-18 04:47:58 UTC

Parallelism

86/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #82,022,193  ·  21 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

0xf9f48af5…4205

0xa6afd3…d132

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x18b8bb2a…c31a

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xb3572c95…9c4a

0x2a68ba…90c5

4 touches
1 conflict

0x9a3068dd…18f1

0x34b655…2a6f

4 touches
1 conflict

0x76d1e78d…7877

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