← previous blocknext block →recent activity

Analyzing

Block #90,028,983

12 transactions · 12 stateful · 2026-07-24 21:52:17 UTC

Parallelism

83/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #90,028,983  ·  12 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

0x10379e8d…3675

0x34b655…2a6f

4 touches
1 conflict

0x1294a92c…f91e

0x34b655…2a6f

4 touches
1 conflict

0x40ee7a94…d6a8

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4988b8a5…a365

0x34b655…2a6f

4 touches
1 conflict

0x542ff3d0…3fa7

0x34b655…2a6f

4 touches
1 conflict

0x7c09c53e…64b4

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