← previous blocknext block →recent activity

Analyzing

Block #82,758,498

26 transactions · 19 stateful · 2026-06-21 14:43:33 UTC

Parallelism

73/100

Blocked

42%

Avg conflicts / tx

0.85

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #82,758,498  ·  26 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x8b305a3b…1c35

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xde1a0ee7…c75b

0x34b655…2a6f

4 touches
1 conflict

0x033cf007…136d

0x34b655…2a6f

4 touches
1 conflict

0x08913286…f0df

0x34b655…2a6f

4 touches
1 conflict

0x109d8a52…a7b7

0x34b655…2a6f

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

10 conflicts on slot 0x8b305a3b6b…0c1c35

← previous block·next block →recent activity