← previous blocknext block →recent activity

Analyzing

Block #82,340,839

21 transactions · 17 stateful · 2026-06-19 16:13:08 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #82,340,839  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x745a7fd6…5fea

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x1b3114cd…5e2d

0xa6afd3…d132

6 touches
3 conflicts

0x66c5e348…51d0

0xa6afd3…d132

6 touches
3 conflicts

0xfbcbd3a5…d407

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0029

0x1b6862…e19c

4 touches
1 conflict

0x6b1259e6…4e0e

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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 0x745a7fd6fd…595fea

← previous block·next block →recent activity