← previous blocknext block →recent activity

Analyzing

Block #82,747,988

28 transactions · 18 stateful · 2026-06-21 13:33:28 UTC

Parallelism

86/100

Blocked

39%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #82,747,988  ·  28 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x216ffe66…1f94

0x34b655…2a6f

6 touches
3 conflicts

0x8b305a3b…1c35

0x34b655…2a6f

6 touches
3 conflicts

0x056e2061…ba40

0x34b655…2a6f

4 touches
1 conflict

0x07bb3f5a…617e

0x34b655…2a6f

4 touches
1 conflict

0x8c09fdbf…2abc

0x34b655…2a6f

4 touches
1 conflict

0x7425a853…a582

0x34b655…2a6f

4 touches
1 conflict

0x74d6c8dd…1695

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity