← previous blocknext block →recent activity

Analyzing

Block #82,796,988

21 transactions · 14 stateful · 2026-06-21 19:00:24 UTC

Parallelism

81/100

Blocked

50%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #82,796,988  ·  21 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

0x5a19ef35…dc70

0x34b655…2a6f

6 touches
3 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

6 touches
3 conflicts

0xab83f300…f8c8

0x34b655…2a6f

6 touches
3 conflicts

0x08913286…f0df

0x34b655…2a6f

6 touches
3 conflicts

0xfcb9138a…3830

0xc8689a…ee79

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xd8bc53a3…c2fe

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

3 conflicts on slot 0x5a19ef3589…3ddc70

← previous block·next block →recent activity