← previous blocknext block →recent activity

Analyzing

Block #90,803,484

17 transactions · 17 stateful · 2026-07-27 15:08:19 UTC

Parallelism

88/100

Blocked

18%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #90,803,484  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xc824469a…642d

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe3c9b04f…1db4

0x34b655…2a6f

4 touches
1 conflict

0xea6c2d78…6ac9

0x34b655…2a6f

4 touches
1 conflict

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0x428b6e5b…8909

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