← previous blocknext block →recent activity

Analyzing

Block #82,965,663

24 transactions · 17 stateful · 2026-06-22 13:47:40 UTC

Parallelism

88/100

Blocked

35%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #82,965,663  ·  24 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

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f1

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xb4c35fcd…43ae

0xa6afd3…d132

4 touches
1 conflict

0x06c59b8c…89c0

0x34b655…2a6f

4 touches
1 conflict

0x5d46e6a0…5ed9

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: Perpl

3 conflicts on slot 0x08913286f9…0ff0df

← previous block·next block →recent activity