← previous blocknext block →recent activity

Analyzing

Block #80,330,330

23 transactions · 19 stateful · 2026-06-10 08:51:03 UTC

Parallelism

78/100

Blocked

37%

Avg conflicts / tx

0.61

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #80,330,330  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x80afd9d9…57cf

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x14c748de…01bd

0x065c9d…c394

5 touches
3 conflicts

0x40970e69…da50

0x69df8a…6292

4 touches
1 conflict

0x8cf3d245…1d0d

0x69df8a…6292

4 touches
1 conflict

0xa605468c…1bfc

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

6 conflicts on slot 0x13a54fa2d3…a35ae3

← previous block·next block →recent activity