← previous blocknext block →recent activity

Analyzing

Block #80,629,130

21 transactions · 14 stateful · 2026-06-11 18:03:43 UTC

Parallelism

90/100

Blocked

14%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #80,629,130  ·  21 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x0672e4a2…8d1f

0x34b655…2a6f

4 touches
1 conflict

0x0f2d78b1…7363

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x455b104f…3960

0xea1b8e…c5ec

2 touches
0 conflicts

0x4771d6f3…23a9

0xea1b8e…c5ec

2 touches
0 conflicts

0x9c8d6dd6…d619

0xea1b8e…c5ec

2 touches
0 conflicts

0x9c8d6dd6…d61a

0xea1b8e…c5ec

2 touches
0 conflicts

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

1 conflict on slot 0x0672e4a279…2f8d1f

← previous block·next block →recent activity