← previous blocknext block →recent activity

Analyzing

Block #82,965,577

20 transactions · 17 stateful · 2026-06-22 13:47:06 UTC

Parallelism

80/100

Blocked

35%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #82,965,577  ·  20 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x5581d709…ab77

0x2a68ba…90c5

4 touches
1 conflict

0x76d1e78d…7877

0x40c49f…2af0

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x217bd767…b79e

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x6779811e…481e

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 0xf2f76ab392…f3623e

← previous block·next block →recent activity