← previous blocknext block →recent activity

Analyzing

Block #83,037,895

18 transactions · 14 stateful · 2026-06-22 21:51:13 UTC

Parallelism

78/100

Blocked

50%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,037,895  ·  18 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

0x08913286…f0df

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0xceb535f3…19cf

0x34b655…2a6f

8 touches
6 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

6 touches
3 conflicts

0xea80dbfe…9552

0x34b655…2a6f

6 touches
3 conflicts

0xf7e84d35…ad5c

0x34b655…2a6f

6 touches
3 conflicts

0x36a49c16…89b9

0xc8689a…ee79

6 touches
3 conflicts

0x63c900f4…2600

0x34b655…2a6f

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

6 conflicts on slot 0x08913286f9…0ff0df

← previous block·next block →recent activity