← previous blocknext block →recent activity

Analyzing

Block #80,484,742

24 transactions · 20 stateful · 2026-06-11 01:59:53 UTC

Parallelism

75/100

Blocked

40%

Avg conflicts / tx

0.54

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #80,484,742  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

8 touches
6 conflicts

0x217bd767…b79e

0x34b655…2a6f

6 touches
3 conflicts

0xd1f41160…19da

0x34b655…2a6f

6 touches
3 conflicts

0xecb2b88e…24c8

0x34b655…2a6f

6 touches
3 conflicts

0xfe3d37ee…6e67

0x34b655…2a6f

6 touches
3 conflicts

0x5701e33e…a3fe

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x25d30ad6…a8ec

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity