← previous blocknext block →recent activity

Analyzing

Block #74,779,221

32 transactions · 21 stateful · 2026-05-15 15:33:46 UTC

Parallelism

75/100

Blocked

71%

Avg conflicts / tx

1.31

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,779,221  ·  32 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x35548b82…2b17

0xd32edf…ff58

15 touches
28 conflicts

0x388e001a…7e04

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…001a

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002a

0x1b6862…e19c

8 touches
6 conflicts

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: 0xd32edf66…9fff58

28 conflicts on slot 0x35548b82a7…c52b17

← previous block·next block →recent activity