← previous blocknext block →recent activity

Analyzing

Block #84,509,687

25 transactions · 21 stateful · 2026-06-29 17:30:20 UTC

Parallelism

88/100

Blocked

29%

Avg conflicts / tx

0.28

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,509,687  ·  25 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

0xe41f8863…29a4

0xa6afd3…d132

4 touches
1 conflict

0x3da49e5d…8067

0x34b655…2a6f

4 touches
1 conflict

0x89ef0dba…31e2

0x34b655…2a6f

4 touches
1 conflict

0x8a7af3fd…72a6

0x34b655…2a6f

4 touches
1 conflict

0x8a7af3fd…72a7

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe99d8e68…a16e

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 0xe41f886384…3929a4

← previous block·next block →recent activity