← previous blocknext block →recent activity

Analyzing

Block #90,525,411

27 transactions · 17 stateful · 2026-07-26 15:49:25 UTC

Parallelism

89/100

Blocked

35%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,525,411  ·  27 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x80afd9d9…57cf

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0x48cba2…b48b

4 touches
1 conflict

0x21898044…a071

0x065c9d…c394

4 touches
1 conflict

0x5b313a49…3021

0x065c9d…c394

4 touches
1 conflict

0xb4e0a934…5fc7

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1543

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 0x80afd9d9f2…3f57cf

← previous block·next block →recent activity