← previous blocknext block →recent activity

Analyzing

Block #80,787,731

19 transactions · 16 stateful · 2026-06-12 11:41:05 UTC

Parallelism

74/100

Blocked

44%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #80,787,731  ·  19 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

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x114324a9…6d5e

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x557cd4fa…228c

0x2a68ba…90c5

4 touches
1 conflict

0x1504aa7b…24ad

0xa6afd3…d132

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x80afd9d9…57cf

0x065c9d…c394

4 touches
1 conflict

0xa2fefd7c…2f6d

0x34b655…2a6f

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

6 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity