← previous blocknext block →recent activity

Analyzing

Block #80,328,647

20 transactions · 18 stateful · 2026-06-10 08:39:51 UTC

Parallelism

80/100

Blocked

33%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #80,328,647  ·  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

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xe4afaa2f…3b69

0xa6afd3…d132

6 touches
3 conflicts

0x7b9a42f7…7b88

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x9f189645…0acf

0xee8c0e…1242

4 touches
1 conflict

0x7c6d3d6d…9deb

0x34b655…2a6f

4 touches
1 conflict

0xb05cd4f5…73d0

0x69df8a…6292

4 touches
1 conflict

0xdb067026…9eb8

0x69df8a…6292

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