← previous blocknext block →recent activity

Analyzing

Block #90,790,523

18 transactions · 15 stateful · 2026-07-27 14:03:06 UTC

Parallelism

78/100

Blocked

53%

Avg conflicts / tx

0.56

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,790,523  ·  18 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

6 touches
3 conflicts

0x0e91dab0…e1b2

0xa6afd3…d132

6 touches
3 conflicts

0xbf78ee7f…e7fd

0x34b655…2a6f

6 touches
3 conflicts

0x2d7b3d63…c856

0x34b655…2a6f

4 touches
1 conflict

0x329f2f7d…dcff

0x34b655…2a6f

4 touches
1 conflict

0x65c50a7f…f491

0x34b655…2a6f

4 touches
1 conflict

0x775a8ad3…8307

0x34b655…2a6f

4 touches
1 conflict

0x87923ecf…1f09

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity