← previous blocknext block →recent activity

Analyzing

Block #80,223,962

21 transactions · 17 stateful · 2026-06-09 21:01:48 UTC

Parallelism

81/100

Blocked

47%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #80,223,962  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x80afd9d9…57cf

0x065c9d…c394

6 touches
3 conflicts

0x0462262d…a368

0x34b655…2a6f

4 touches
1 conflict

0x217bd767…b79e

0x34b655…2a6f

4 touches
1 conflict

0x2e991906…20db

0x34b655…2a6f

4 touches
1 conflict

0x3f24a374…6bc3

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity