← previous blocknext block →recent activity

Analyzing

Block #84,315,509

12 transactions · 8 stateful · 2026-06-28 19:55:42 UTC

Parallelism

75/100

Blocked

38%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,315,509  ·  12 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

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0x610aa855…5ecd

0x34b655…2a6f

4 touches
1 conflict

0x69455e0f…24ec

0x34b655…2a6f

4 touches
1 conflict

0x7ee6007b…fd68

0x34b655…2a6f

4 touches
1 conflict

0xc0b9bd73…7f1c

0x34b655…2a6f

4 touches
1 conflict

0xd58b9a66…1c23

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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