← previous blocknext block →recent activity

Analyzing

Block #84,333,344

14 transactions · 12 stateful · 2026-06-28 21:54:33 UTC

Parallelism

79/100

Blocked

33%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,333,344  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x975680c7…0e39

0xa6afd3…d132

4 touches
1 conflict

0x0f8965bb…e238

0x34b655…2a6f

4 touches
1 conflict

0x178fe051…465a

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x3732c6c9…ded6

0x34b655…2a6f

4 touches
1 conflict

0x3b0a8356…a2b6

0x34b655…2a6f

4 touches
1 conflict

0x7506443a…4820

0x34b655…2a6f

4 touches
1 conflict

0x781a2c9b…f540

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 0x975680c7cb…460e39

← previous block·next block →recent activity