← previous blocknext block →recent activity

Analyzing

Block #90,885,711

15 transactions · 14 stateful · 2026-07-27 22:02:05 UTC

Parallelism

67/100

Blocked

57%

Avg conflicts / tx

1.13

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,885,711  ·  15 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

0x731f2745…9370

0xa6afd3…d132

10 touches
10 conflicts

0x00000000…003d

0xa6afd3…d132

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x53f393fa…00b9

0x34b655…2a6f

6 touches
3 conflicts

0xb5c4826d…bdd6

0x2b46c0…1669

4 touches
1 conflict

0xdb067026…9eb8

0x2b46c0…1669

4 touches
1 conflict

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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

10 conflicts on slot 0x731f274569…029370

← previous block·next block →recent activity