← previous blocknext block →recent activity

Analyzing

Block #80,448,810

24 transactions · 20 stateful · 2026-06-10 22:00:29 UTC

Parallelism

79/100

Blocked

35%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #80,448,810  ·  24 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

0xdc120748…ff36

0xa6afd3…d132

10 touches
10 conflicts

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xdf708ee7…1fcf

0xc8689a…ee79

4 touches
1 conflict

0x40970e69…da50

0x69df8a…6292

4 touches
1 conflict

0x8cf3d245…1d0d

0x69df8a…6292

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: 0xa6afd386…b0d132

10 conflicts on slot 0xdc120748a9…41ff36

← previous block·next block →recent activity