← previous blocknext block →recent activity

Analyzing

Block #80,586,189

22 transactions · 20 stateful · 2026-06-11 13:16:47 UTC

Parallelism

77/100

Blocked

40%

Avg conflicts / tx

0.55

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #80,586,189  ·  22 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

0x90f07a4f…d932

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x9cf5ac50…1be9

0xa6afd3…d132

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0x56153262…21ce

0x34b655…2a6f

4 touches
1 conflict

0x78cbb28a…27c3

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