← previous blocknext block →recent activity

Analyzing

Block #80,484,261

23 transactions · 20 stateful · 2026-06-11 01:56:41 UTC

Parallelism

87/100

Blocked

35%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #80,484,261  ·  23 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x08943ea2…ed03

0x754704…b603

6 touches
3 conflicts

0x90f07a4f…d932

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x80afd9d9…57cf

0x065c9d…c394

4 touches
1 conflict

0xbd2bbb70…94b6

0x065c9d…c394

4 touches
1 conflict

0xd77e90ec…8c04

0x3bd359…433a

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

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)

3 conflicts on slot 0x08943ea26c…67ed03

← previous block·next block →recent activity