← previous blocknext block →recent activity

Analyzing

Block #80,823,648

18 transactions · 12 stateful · 2026-06-12 15:40:39 UTC

Parallelism

89/100

Blocked

33%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #80,823,648  ·  18 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x11431f9d…42c5

0x34b655…2a6f

4 touches
1 conflict

0x5f91ee13…5aef

0x34b655…2a6f

4 touches
1 conflict

0x6b47245e…a342

0x34b655…2a6f

4 touches
1 conflict

0x74fd0a9b…3aaa

0x34b655…2a6f

4 touches
1 conflict

0xb9b4eff6…c3ef

0x34b655…2a6f

4 touches
1 conflict

0xd1a8b9bd…6f8c

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity