← previous blocknext block →recent activity

Analyzing

Block #87,735,744

19 transactions · 18 stateful · 2026-07-14 16:28:24 UTC

Parallelism

84/100

Blocked

33%

Avg conflicts / tx

0.58

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,735,744  ·  19 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

0x2caa222d…60af

0x34b655…2a6f

6 touches
3 conflicts

0x315e07b8…9823

0x34b655…2a6f

4 touches
1 conflict

0x47194d03…58a3

0x34b655…2a6f

4 touches
1 conflict

0x6030bece…bf0e

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x9243d2e7…9c5d

0x34b655…2a6f

4 touches
1 conflict

0xa09be165…16b9

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