← previous blocknext block →recent activity

Analyzing

Block #90,789,431

14 transactions · 13 stateful · 2026-07-27 13:57:37 UTC

Parallelism

71/100

Blocked

54%

Avg conflicts / tx

0.71

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,789,431  ·  14 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

0x561ad161…c172

0xa6afd3…d132

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x67bae043…b9f2

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xdb067026…9eb8

0x2b46c0…1669

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4ae3b148…7ed2

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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 0x561ad161ce…23c172

← previous block·next block →recent activity