← previous blocknext block →recent activity

Analyzing

Block #86,657,326

22 transactions · 20 stateful · 2026-07-09 16:18:00 UTC

Parallelism

86/100

Blocked

30%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,657,326  ·  22 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

4 touches
1 conflict

0x5d2e788d…5867

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6426

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xfaef08b1…0696

0x34b655…2a6f

4 touches
1 conflict

0x143dba04…1b98

0xb1dbf0…c0d3

4 touches
1 conflict

0x8a35acfb…d1a8

0xb1dbf0…c0d3

4 touches
1 conflict

0xce827910…ff22

0x065c9d…c394

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