← previous blocknext block →recent activity

Analyzing

Block #82,976,637

19 transactions · 18 stateful · 2026-06-22 15:01:04 UTC

Parallelism

84/100

Blocked

33%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #82,976,637  ·  19 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

0x08913286…f0df

0x34b655…2a6f

6 touches
3 conflicts

0x112cf8ad…6e4f

0xa6afd3…d132

6 touches
3 conflicts

0x7ee6007b…fd68

0x34b655…2a6f

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x5d46e6a0…5ed9

0x40c49f…2af0

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x00000000…001e

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…002e

0x1b6862…e19c

2 touches
0 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: Perpl

3 conflicts on slot 0x08913286f9…0ff0df

← previous block·next block →recent activity