← previous blocknext block →recent activity

Analyzing

Block #88,356,553

22 transactions · 18 stateful · 2026-07-17 13:41:42 UTC

Parallelism

86/100

Blocked

28%

Avg conflicts / tx

0.41

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #88,356,553  ·  22 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

4 touches
1 conflict

0x00ddbbf2…4588

0x34b655…2a6f

4 touches
1 conflict

0x22c17b4e…e07e

0x34b655…2a6f

4 touches
1 conflict

0x22c17b4e…e07f

0x34b655…2a6f

4 touches
1 conflict

0x253bf197…1e1a

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x52a2ba74…f2f6

0x34b655…2a6f

4 touches
1 conflict

0x5c625a40…5965

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

1 conflict on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity