← previous blocknext block →recent activity

Analyzing

Block #87,407,993

17 transactions · 16 stateful · 2026-07-13 03:55:37 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

0.53

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,407,993  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x69c491e3…98d9

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x80bf58f2…be95

0x34b655…2a6f

4 touches
1 conflict

0x87ee379a…cd9e

0x34b655…2a6f

4 touches
1 conflict

0x9769421a…9da5

0x34b655…2a6f

4 touches
1 conflict

0xa690e755…f979

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 0x13a54fa2d3…a35ae3

← previous block·next block →recent activity