← previous blocknext block →recent activity

Analyzing

Block #90,874,677

15 transactions · 14 stateful · 2026-07-27 21:06:35 UTC

Parallelism

73/100

Blocked

50%

Avg conflicts / tx

0.73

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,874,677  ·  15 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xf0c9f082…cdf4

0x34b655…2a6f

4 touches
1 conflict

0xf69bf8bb…421f

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x0eac7709…66c3

0x34b655…2a6f

4 touches
1 conflict

0x18a4f96f…8ed0

0x34b655…2a6f

4 touches
1 conflict

0x24eaf46d…8c2e

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