← previous blocknext block →recent activity

Analyzing

Block #80,586,195

29 transactions · 18 stateful · 2026-06-11 13:16:49 UTC

Parallelism

79/100

Blocked

50%

Avg conflicts / tx

0.69

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #80,586,195  ·  29 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

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

8 touches
6 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

8 touches
6 conflicts

0xd025d7d7…f05a

0x3bd359…433a

6 touches
3 conflicts

0x062543af…4708

0xd32edf…ff58

5 touches
3 conflicts

0x4dd1db39…a996

0x188d58…ea8e

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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: USDC (USDC)

10 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity