← previous blocknext block →recent activity

Analyzing

Block #89,405,707

22 transactions · 21 stateful · 2026-07-22 10:38:10 UTC

Parallelism

77/100

Blocked

38%

Avg conflicts / tx

0.73

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #89,405,707  ·  22 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

0x002fed35…79fa

0x2a68ba…90c5

10 touches
10 conflicts

0x11b69a7e…334e

0x01bff4…1071

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x2a0d5427…2498

0x851145…3f07

8 touches
6 conflicts

0x2bac71c3…3296

0x34b655…2a6f

6 touches
3 conflicts

0x02d895f0…2b93

0x34b655…2a6f

5 touches
3 conflicts

0x508bbf1b…fe95

0x34b655…2a6f

4 touches
1 conflict

0x51d435fc…279a

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: MarginAccount

10 conflicts on slot 0x002fed350f…7379fa

← previous block·next block →recent activity