← previous blocknext block →recent activity

Analyzing

Block #89,846,450

20 transactions · 17 stateful · 2026-07-24 06:33:30 UTC

Parallelism

80/100

Blocked

47%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,846,450  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xc6b1d981…1be2

0xa6afd3…d132

6 touches
3 conflicts

0xc782ec05…5bb2

0xa6afd3…d132

6 touches
3 conflicts

0xd68cd74f…9826

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xafb8e71e…9285

0x34b655…2a6f

4 touches
1 conflict

0xb7a0aeb3…a20f

0x34b655…2a6f

4 touches
1 conflict

0x99f666e3…b2a2

0x3bd359…433a

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 0xc6b1d98106…cc1be2

← previous block·next block →recent activity