← previous blocknext block →recent activity

Analyzing

Block #82,980,195

20 transactions · 17 stateful · 2026-06-22 15:24:51 UTC

Parallelism

80/100

Blocked

41%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #82,980,195  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x8d0d8061…d410

0xc8689a…ee79

4 touches
1 conflict

0x0fde64da…aa3e

0x2a68ba…90c5

4 touches
1 conflict

0x09e07591…a43e

0x851145…3f07

4 touches
1 conflict

0xc660ab51…886f

0x851145…3f07

4 touches
1 conflict

0x112cf8ad…6e4f

0xa6afd3…d132

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity