← previous blocknext block →recent activity

Analyzing

Block #89,666,653

16 transactions · 13 stateful · 2026-07-23 15:25:19 UTC

Parallelism

88/100

Blocked

23%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #89,666,653  ·  16 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

0x989252a1…d812

0xa6afd3…d132

4 touches
1 conflict

0x2840c278…bbc7

0x34b655…2a6f

4 touches
1 conflict

0x2e1f5171…ad2d

0x34b655…2a6f

4 touches
1 conflict

0x43fd3667…094b

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f0

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641e

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641f

0x34b655…2a6f

4 touches
1 conflict

0xdf63e36e…3ce3

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 0x989252a1e8…7ed812

← previous block·next block →recent activity