← previous blocknext block →recent activity

Analyzing

Block #74,774,361

26 transactions · 20 stateful · 2026-05-15 15:01:14 UTC

Parallelism

65/100

Blocked

65%

Avg conflicts / tx

1.69

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,774,361  ·  26 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x4b06a910…57da

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…0001

0xcc67aa…c71c

8 touches
6 conflicts

0x00000000…0000

0xcc67aa…c71c

8 touches
6 conflicts

0xce2b6650…ecc3

0x5c2513…7777

8 touches
6 conflicts

0x44ad89ba…cf83

0x5c2513…7777

8 touches
6 conflicts

0x00c46468…f328

0x3bd359…433a

8 touches
6 conflicts

0xa472d565…9fe4

0x3bd359…433a

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 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

36 conflicts on slot 0x4b06a910c2…c257da

← previous block·next block →recent activity