← previous blocknext block →recent activity

Analyzing

Block #82,749,722

22 transactions · 18 stateful · 2026-06-21 13:45:01 UTC

Parallelism

68/100

Blocked

44%

Avg conflicts / tx

1.05

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #82,749,722  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x8b305a3b…1c35

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xd3a433e6…2fad

0x34b655…2a6f

8 touches
6 conflicts

0x8b305a3b…1c34

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xd36a87e0…ea15

0x34b655…2a6f

4 touches
1 conflict

0xd800e635…b1d7

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

15 conflicts on slot 0x8b305a3b6b…0c1c35

← previous block·next block →recent activity