← previous blocknext block →recent activity

Analyzing

Block #80,931,506

16 transactions · 12 stateful · 2026-06-13 03:39:56 UTC

Parallelism

88/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #80,931,506  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x4039b31f…0f4a

0x754704…b603

4 touches
1 conflict

0x82dd2252…e1ce

0x34b655…2a6f

4 touches
1 conflict

0x94f5fc74…a10d

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f0

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f1

0x34b655…2a6f

4 touches
1 conflict

0xfb3d8d6a…9f41

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0004

0x5afd3e…7620

4 touches
1 conflict

0x9b80bd2e…53c6

0x5afd3e…7620

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: USDC (USDC)

1 conflict on slot 0x4039b31fcf…cb0f4a

← previous block·next block →recent activity