← previous blocknext block →recent activity

Analyzing

Block #90,878,699

17 transactions · 17 stateful · 2026-07-27 21:26:49 UTC

Parallelism

82/100

Blocked

41%

Avg conflicts / tx

0.59

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,878,699  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x449d101e…ea3f

0xa6afd3…d132

6 touches
3 conflicts

0xd7badc5e…8c2b

0xa6afd3…d132

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0x48cba2…b48b

4 touches
1 conflict

0x24eaf46d…8c2e

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x26d1c221…4d2a

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