← previous blocknext block →recent activity

Analyzing

Block #82,667,319

22 transactions · 16 stateful · 2026-06-21 04:34:41 UTC

Parallelism

91/100

Blocked

31%

Avg conflicts / tx

0.23

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #82,667,319  ·  22 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x8a7af3fd…72a7

0x34b655…2a6f

4 touches
1 conflict

0xd24a5afe…0651

0x5afd3e…7620

4 touches
1 conflict

0x5820aa20…9c7d

0x5afd3e…7620

4 touches
1 conflict

0x5540f956…69e8

0x065c9d…c394

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6e

0x188d58…ea8e

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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

1 conflict on slot 0x8a7af3fdbb…2b72a7

← previous block·next block →recent activity