← previous blocknext block →recent activity

Analyzing

Block #80,248,583

23 transactions · 17 stateful · 2026-06-09 23:46:05 UTC

Parallelism

74/100

Blocked

53%

Avg conflicts / tx

0.78

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #80,248,583  ·  23 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

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x692de2da…5986

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x179fe783…6945

0xa6afd3…d132

6 touches
3 conflicts

0xc5dc29f0…f0c6

0x34b655…2a6f

6 touches
3 conflicts

0x7531e9d9…196d

0xa6afd3…d132

6 touches
3 conflicts

0x40970e69…da50

0x69df8a…6292

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: Kuru Exchange: Market-WETH/USDC

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity