← previous blocknext block →recent activity

Analyzing

Block #84,237,973

19 transactions · 17 stateful · 2026-06-28 11:19:15 UTC

Parallelism

84/100

Blocked

35%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,237,973  ·  19 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

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x705f195d…cc32

0x34b655…2a6f

4 touches
1 conflict

0xa48fbfad…fb17

0x34b655…2a6f

4 touches
1 conflict

0xe2e45419…f17b

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x9951b6b0…22d0

0x40c49f…2af0

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

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