← previous blocknext block →recent activity

Analyzing

Block #80,166,020

24 transactions · 17 stateful · 2026-06-09 14:35:24 UTC

Parallelism

79/100

Blocked

47%

Avg conflicts / tx

0.46

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #80,166,020  ·  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

0xd16df6cd…5532

0x40c49f…2af0

6 touches
3 conflicts

0x833ebd97…5abb

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0xd859e0de…279b

0x34b655…2a6f

4 touches
1 conflict

0xf5310ef7…485a

0x40c49f…2af0

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x213ee207…a151

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: 0x40c49f17…d22af0

3 conflicts on slot 0xd16df6cdbe…065532

← previous block·next block →recent activity