← previous blocknext block →recent activity

Analyzing

Block #90,516,879

26 transactions · 20 stateful · 2026-07-26 15:06:30 UTC

Parallelism

81/100

Blocked

40%

Avg conflicts / tx

0.46

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,516,879  ·  26 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xabd0bcfc…64e2

0x34b655…2a6f

6 touches
3 conflicts

0x2491d756…b71c

0xa6afd3…d132

6 touches
3 conflicts

0x19439a65…eb51

0x34b655…2a6f

4 touches
1 conflict

0x310afe2c…83e1

0x34b655…2a6f

4 touches
1 conflict

0x6127c8ac…3f6e

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x714420ba…96c5

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