← previous blocknext block →recent activity

Analyzing

Block #86,153,897

23 transactions · 17 stateful · 2026-07-07 08:11:53 UTC

Parallelism

87/100

Blocked

35%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,153,897  ·  23 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

0xaf5901cf…b635

0xd32edf…ff58

5 touches
3 conflicts

0x77ed432f…fa04

0x065c9d…c394

4 touches
1 conflict

0x584cbe31…38e5

0x34b655…2a6f

4 touches
1 conflict

0x2f8946d7…cdf9

0x065c9d…c394

4 touches
1 conflict

0xde398ff4…00ca

0x34b655…2a6f

4 touches
1 conflict

0xec0e0220…cb90

0x34b655…2a6f

4 touches
1 conflict

0x0333cb9c…0527

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