← previous blocknext block →recent activity

Analyzing

Block #80,290,265

22 transactions · 19 stateful · 2026-06-10 04:23:56 UTC

Parallelism

73/100

Blocked

42%

Avg conflicts / tx

0.82

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #80,290,265  ·  22 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

0xb4e0a934…5fc7

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x21898044…a071

0x065c9d…c394

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x80afd9d9…57cf

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x11f2aded…153a

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 0xb4e0a934b9…435fc7

← previous block·next block →recent activity