← previous blocknext block →recent activity

Analyzing

Block #82,659,318

25 transactions · 20 stateful · 2026-06-21 03:41:03 UTC

Parallelism

76/100

Blocked

40%

Avg conflicts / tx

0.4

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #82,659,318  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xb3572c95…9c4a

0x2a68ba…90c5

4 touches
1 conflict

0x7e10454f…4d9e

0xa6afd3…d132

4 touches
1 conflict

0x00000000…0000

0xd5b70d…615b

4 touches
1 conflict

0x00000000…0003

0xd5b70d…615b

4 touches
1 conflict

0x00000000…0004

0xd5b70d…615b

4 touches
1 conflict

0x2fd12b6c…02cc

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