← previous blocknext block →recent activity

Analyzing

Block #80,328,798

25 transactions · 17 stateful · 2026-06-10 08:40:51 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.68

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

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

0x13a54fa2…5ae3

0x2a68ba…90c5

10 touches
10 conflicts

0x7b9a42f7…7b88

0xa6afd3…d132

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0xdf708ee7…1fcf

0xc8689a…ee79

6 touches
3 conflicts

0x40970e69…da50

0x69df8a…6292

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0xd16df6cd…5532

0x40c49f…2af0

6 touches
3 conflicts

0xf5310ef7…485a

0x40c49f…2af0

6 touches
3 conflicts

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

10 conflicts on slot 0x13a54fa2d3…a35ae3

← previous block·next block →recent activity