← previous blocknext block →recent activity

Analyzing

Block #82,538,694

29 transactions · 22 stateful · 2026-06-20 14:12:56 UTC

Parallelism

90/100

Blocked

27%

Avg conflicts / tx

0.24

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #82,538,694  ·  29 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x557cd4fa…228c

0x2a68ba…90c5

4 touches
1 conflict

0x03fb27fd…0c06

0x34b655…2a6f

4 touches
1 conflict

0x32cee552…1fc6

0x34b655…2a6f

4 touches
1 conflict

0x41ea96d8…b4de

0x34b655…2a6f

4 touches
1 conflict

0x63c900f4…2600

0x34b655…2a6f

4 touches
1 conflict

0x6b47245e…a342

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

3 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity