← previous blocknext block →recent activity

Analyzing

Block #74,454,356

39 transactions · 31 stateful · 2026-05-14 03:20:29 UTC

Parallelism

85/100

Blocked

52%

Avg conflicts / tx

0.87

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,454,356  ·  39 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

0x602995d3…d6e1

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…001b

0x1b6862…e19c

8 touches
6 conflicts

0xcb45d9d6…cb83

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0xa472d565…9fe4

0x3bd359…433a

8 touches
6 conflicts

0x00c46468…f328

0x3bd359…433a

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x44ad89ba…cf83

0x5c2513…7777

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

15 conflicts on slot 0x602995d3b2…aed6e1

← previous block·next block →recent activity