← previous blocknext block →recent activity

Analyzing

Block #90,698,353

18 transactions · 17 stateful · 2026-07-27 06:19:25 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

0.89

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,698,353  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

10 touches
10 conflicts

0x538f77c2…a9e7

0xa6afd3…d132

8 touches
6 conflicts

0x0e91dab0…e1b2

0xa6afd3…d132

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0x5778d110…d2e6

0xc8689a…ee79

6 touches
3 conflicts

0xd6bd849a…5597

0x2a68ba…90c5

6 touches
3 conflicts

0x8cf3d245…1d0d

0x2b46c0…1669

6 touches
3 conflicts

0xdb067026…9eb8

0x2b46c0…1669

6 touches
3 conflicts

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 0x889d5e90c7…59929a

← previous block·next block →recent activity