← previous blocknext block →recent activity

Analyzing

Block #88,350,775

21 transactions · 19 stateful · 2026-07-17 13:02:42 UTC

Parallelism

76/100

Blocked

37%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #88,350,775  ·  21 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

0x889d5e90…929a

0x2a68ba…90c5

8 touches
6 conflicts

0x62b86e44…980e

0x851145…3f07

6 touches
3 conflicts

0x00000000…003d

0x851145…3f07

6 touches
3 conflicts

0x8649e48f…941c

0xc8689a…ee79

4 touches
1 conflict

0x7a12283f…b18a

0x2b46c0…1669

4 touches
1 conflict

0x915c095e…c1e5

0x2b46c0…1669

4 touches
1 conflict

0xcfe06a18…b5b5

0x2b46c0…1669

4 touches
1 conflict

0xd8fd2add…50fc

0x2b46c0…1669

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

6 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity