← previous blocknext block →recent activity

Analyzing

Block #85,962,751

21 transactions · 16 stateful · 2026-07-06 10:55:46 UTC

Parallelism

86/100

Blocked

38%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #85,962,751  ·  21 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

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x66f473d3…2d03

0xa6afd3…d132

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa4f80979…4d71

0x065c9d…c394

4 touches
1 conflict

0xd35bb5ac…3586

0x065c9d…c394

4 touches
1 conflict

0x260a92ae…423e

0x34b655…2a6f

4 touches
1 conflict

0x32adb2c4…32c5

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

← previous block·next block →recent activity