← previous blocknext block →recent activity

Analyzing

Block #80,683,749

36 transactions · 17 stateful · 2026-06-12 00:07:47 UTC

Parallelism

89/100

Blocked

35%

Avg conflicts / tx

0.31

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #80,683,749  ·  36 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

0x00000000…0002

0x6fae99…a56d

8 touches
6 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0x0e8feb30…4078

0x065c9d…c394

5 touches
3 conflicts

0xf853eb8e…401e

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…7212

0x34b655…2a6f

4 touches
1 conflict

0xb33ff823…1188

0x065c9d…c394

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x3f4cc881…b165

0xd32edf…ff58

3 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: 0x6fae9933…7ba56d

6 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity