← previous blocknext block →recent activity

Analyzing

Block #88,040,329

19 transactions · 16 stateful · 2026-07-16 02:25:42 UTC

Parallelism

79/100

Blocked

50%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #88,040,329  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x034d14da…9f5f

0x34b655…2a6f

4 touches
1 conflict

0x17fbe072…2ea6

0x34b655…2a6f

4 touches
1 conflict

0x28d4261c…56c7

0x34b655…2a6f

4 touches
1 conflict

0x28d4261c…56c8

0x34b655…2a6f

4 touches
1 conflict

0x34bcdc05…6689

0x34b655…2a6f

4 touches
1 conflict

0x410b84ab…1dbc

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