← previous blocknext block →recent activity

Analyzing

Block #82,757,173

21 transactions · 15 stateful · 2026-06-21 14:34:43 UTC

Parallelism

76/100

Blocked

53%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #82,757,173  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x6fbc2e5a…e69c

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x326a02b5…8dad

0x34b655…2a6f

10 touches
10 conflicts

0x8b305a3b…1c35

0x34b655…2a6f

6 touches
3 conflicts

0xdc921364…4680

0x34b655…2a6f

6 touches
3 conflicts

0xfab1627b…b819

0x34b655…2a6f

4 touches
1 conflict

0xbbb9fa77…d121

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

10 conflicts on slot 0x6fbc2e5a11…b3e69c

← previous block·next block →recent activity