← previous blocknext block →recent activity

Analyzing

Block #80,251,429

25 transactions · 19 stateful · 2026-06-10 00:05:02 UTC

Parallelism

72/100

Blocked

47%

Avg conflicts / tx

0.8

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #80,251,429  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x36d366fe…7adc

0xa6afd3…d132

8 touches
6 conflicts

0xef65bff3…7c9d

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x80afd9d9…57cf

0x065c9d…c394

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x40970e69…da50

0x69df8a…6292

4 touches
1 conflict

0x8cf3d245…1d0d

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 0x36d366fe30…fe7adc

← previous block·next block →recent activity