← previous blocknext block →recent activity

Analyzing

Block #82,667,912

24 transactions · 19 stateful · 2026-06-21 04:38:38 UTC

Parallelism

75/100

Blocked

37%

Avg conflicts / tx

0.83

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #82,667,912  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x6af306bb…2e81

0x3bd359…433a

10 touches
10 conflicts

0x70e7f9a3…861d

0xd32edf…ff58

9 touches
10 conflicts

0x09beabbc…065c

0x188d58…ea8e

8 touches
6 conflicts

0x09beabbc…065e

0x188d58…ea8e

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0018

0x1b6862…e19c

8 touches
6 conflicts

0xcb45d9d6…cb80

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 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: Wrapped MON (WMON)

10 conflicts on slot 0x6af306bb1d…092e81

← previous block·next block →recent activity