← previous blocknext block →recent activity

Analyzing

Block #80,270,185

19 transactions · 16 stateful · 2026-06-10 02:10:07 UTC

Parallelism

84/100

Blocked

44%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #80,270,185  ·  19 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

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xa40acd53…13f9

0xd32edf…ff58

5 touches
3 conflicts

0x80afd9d9…57cf

0x065c9d…c394

4 touches
1 conflict

0xdbc6e634…e165

0x1b6862…e19c

4 touches
1 conflict

0x78ac9dba…5f85

0x065c9d…c394

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x7d42dc8b…fdb6

0x2a68ba…90c5

4 touches
1 conflict

0x217bd767…b79e

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

3 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity