← previous blocknext block →recent activity

Analyzing

Block #90,240,477

18 transactions · 17 stateful · 2026-07-25 15:41:12 UTC

Parallelism

72/100

Blocked

47%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,240,477  ·  18 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

0x9ff176a9…152e

0x065c9d…c394

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x5540f956…69e8

0x065c9d…c394

6 touches
3 conflicts

0xb69dd898…3e02

0x34b655…2a6f

6 touches
3 conflicts

0x4f267385…cc89

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

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-MON/USDC

3 conflicts on slot 0x9ff176a9ad…67152e

← previous block·next block →recent activity