← previous blocknext block →recent activity

Analyzing

Block #92,770,897

17 transactions · 16 stateful · 2026-08-03 12:09:15 UTC

Parallelism

82/100

Blocked

38%

Avg conflicts / tx

0.41

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #92,770,897  ·  17 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

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x342fbbca…d443

0x40c49f…2af0

4 touches
1 conflict

0xd8ba62fe…cfde

0x40c49f…2af0

4 touches
1 conflict

0xffa7d0a4…b10a

0x40c49f…2af0

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0xa435dee8…f2be

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

3 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity