← previous blocknext block →recent activity

Analyzing

Block #89,386,183

20 transactions · 18 stateful · 2026-07-22 08:27:36 UTC

Parallelism

90/100

Blocked

28%

Avg conflicts / tx

0.3

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #89,386,183  ·  20 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x28f324ed…9db7

0x34b655…2a6f

4 touches
1 conflict

0x2fcc0ee9…73e2

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x508bbf1b…fe95

0x34b655…2a6f

4 touches
1 conflict

0x5d9494db…bf47

0x34b655…2a6f

4 touches
1 conflict

0x67f87cdf…e5b6

0x34b655…2a6f

4 touches
1 conflict

0x6e0e8837…2e59

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