← previous blocknext block →recent activity

Analyzing

Block #86,222,029

33 transactions · 20 stateful · 2026-07-07 15:46:45 UTC

Parallelism

88/100

Blocked

35%

Avg conflicts / tx

0.27

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,222,029  ·  33 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

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf19e7420…bdae

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x77ed432f…fa04

0x065c9d…c394

4 touches
1 conflict

0x95523e2a…4c01

0x065c9d…c394

4 touches
1 conflict

0x077d58c3…8ed7

0x34b655…2a6f

4 touches
1 conflict

0x109d8a52…a7b7

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