← previous blocknext block →recent activity

Analyzing

Block #80,164,645

19 transactions · 17 stateful · 2026-06-09 14:26:14 UTC

Parallelism

84/100

Blocked

41%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #80,164,645  ·  19 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

0x90f07a4f…d932

0x34b655…2a6f

6 touches
3 conflicts

0xf5310ef7…485a

0x40c49f…2af0

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x1d6cb721…c88c

0x34b655…2a6f

4 touches
1 conflict

0x2aab0897…78f7

0x34b655…2a6f

4 touches
1 conflict

0x444c3ac5…2a12

0x34b655…2a6f

4 touches
1 conflict

0x5ba4db2b…2f04

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 0x90f07a4ff9…b3d932

← previous block·next block →recent activity