← previous blocknext block →recent activity

Analyzing

Block #87,350,308

17 transactions · 16 stateful · 2026-07-12 21:29:47 UTC

Parallelism

82/100

Blocked

31%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,350,308  ·  17 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

4 touches
1 conflict

0x35d95fb0…db9e

0x34b655…2a6f

4 touches
1 conflict

0x35d95fb0…db9f

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xf29e5320…ce2d

0x34b655…2a6f

4 touches
1 conflict

0xf9e23360…8ef7

0x34b655…2a6f

4 touches
1 conflict

0xfc069c43…5538

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4a2

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 0x0000000000…00003d

← previous block·next block →recent activity