← previous blocknext block →recent activity

Analyzing

Block #82,586,564

38 transactions · 26 stateful · 2026-06-20 19:33:17 UTC

Parallelism

82/100

Blocked

38%

Avg conflicts / tx

0.74

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #82,586,564  ·  38 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

14 touches
21 conflicts

0xd3a433e6…2fad

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0x8b305a3b…1c34

0x34b655…2a6f

12 touches
15 conflicts

0x75c94a8e…36b9

0x34b655…2a6f

9 touches
10 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xfe39a1f7…8eb0

0x34b655…2a6f

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: Perpl

21 conflicts on slot 0x8b305a3b6b…0c1c35

← previous block·next block →recent activity