← previous blocknext block →recent activity

Analyzing

Block #84,036,730

18 transactions · 15 stateful · 2026-06-27 12:58:48 UTC

Parallelism

72/100

Blocked

53%

Avg conflicts / tx

0.72

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,036,730  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0x2d5c395b…6b5a

0xa6afd3…d132

8 touches
6 conflicts

0x7c5260f4…bd96

0xa6afd3…d132

8 touches
6 conflicts

0x9540632c…78a0

0x34b655…2a6f

6 touches
3 conflicts

0x6f6fc26c…3e34

0x34b655…2a6f

6 touches
3 conflicts

0xe02484a6…c32e

0xc8689a…ee79

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe560375e…4626

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity