← previous blocknext block →recent activity

Analyzing

Block #87,617,183

18 transactions · 16 stateful · 2026-07-14 03:15:24 UTC

Parallelism

78/100

Blocked

50%

Avg conflicts / tx

0.78

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,617,183  ·  18 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

8 touches
6 conflicts

0xd93edb3f…94ec

0x34b655…2a6f

6 touches
3 conflicts

0xd8834cf3…0004

0x34b655…2a6f

4 touches
1 conflict

0x2697123c…8526

0x34b655…2a6f

4 touches
1 conflict

0x69ce640b…884a

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4ab

0x34b655…2a6f

4 touches
1 conflict

0x81ca8c9e…28cb

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

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

6 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity