← previous blocknext block →recent activity

Analyzing

Block #82,969,795

23 transactions · 20 stateful · 2026-06-22 14:15:18 UTC

Parallelism

74/100

Blocked

45%

Avg conflicts / tx

0.74

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #82,969,795  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xb245fe36…d765

0x34b655…2a6f

4 touches
1 conflict

0xc3ac1732…1dbb

0x34b655…2a6f

4 touches
1 conflict

0x557cd4fa…228c

0x2a68ba…90c5

4 touches
1 conflict

0x08913286…f0df

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

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

6 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity