← previous blocknext block →recent activity

Analyzing

Block #82,437,827

22 transactions · 18 stateful · 2026-06-20 03:00:41 UTC

Parallelism

86/100

Blocked

33%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #82,437,827  ·  22 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

0x6f58168d…ea24

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x5b6af007…0f35

0x34b655…2a6f

6 touches
3 conflicts

0x08913286…f0df

0x34b655…2a6f

6 touches
3 conflicts

0xcb02fad5…9e3e

0x34b655…2a6f

6 touches
3 conflicts

0xd01910c9…9418

0x34b655…2a6f

5 touches
3 conflicts

0x7e17e82a…9748

0x34b655…2a6f

4 touches
1 conflict

0x957c875f…b3f9

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

3 conflicts on slot 0x6f58168d48…e3ea24

← previous block·next block →recent activity