← previous blocknext block →recent activity

Analyzing

Block #86,625,775

25 transactions · 17 stateful · 2026-07-09 12:45:51 UTC

Parallelism

88/100

Blocked

35%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,625,775  ·  25 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

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xc19e8f12…f625

0xd32edf…ff58

5 touches
3 conflicts

0x460b8864…a46a

0x065c9d…c394

5 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xfaef08b1…0696

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0000

0x0d73bf…be07

2 touches
0 conflicts

0x00000000…0002

0x0d73bf…be07

2 touches
0 conflicts

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 0x92d610a6f9…379a40

← previous block·next block →recent activity