← previous blocknext block →recent activity

Analyzing

Block #80,060,162

24 transactions · 20 stateful · 2026-06-09 02:50:19 UTC

Parallelism

83/100

Blocked

30%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #80,060,162  ·  24 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x119a07d3…7a1f

0xd32edf…ff58

5 touches
3 conflicts

0x7170c140…36bc

0x34b655…2a6f

4 touches
1 conflict

0x90f07a4f…d932

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xca2926e0…61b5

0x34b655…2a6f

4 touches
1 conflict

0xcdc8b4bb…7bce

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

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: Perpl

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity