← previous blocknext block →recent activity

Analyzing

Block #82,018,807

16 transactions · 9 stateful · 2026-06-18 04:25:24 UTC

Parallelism

88/100

Blocked

22%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #82,018,807  ·  16 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

0x9fb55ee7…8ecc

0xa6afd3…d132

4 touches
1 conflict

0x1d6cb721…c88c

0x34b655…2a6f

4 touches
1 conflict

0x2ca0bb85…3363

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f0

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f1

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd30f9e74…d404

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 0x9fb55ee7ce…5b8ecc

← previous block·next block →recent activity