← previous blocknext block →recent activity

Analyzing

Block #73,789,754

32 transactions · 24 stateful · 2026-05-11 01:34:13 UTC

Parallelism

72/100

Blocked

58%

Avg conflicts / tx

1.41

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,789,754  ·  32 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

0x5685e874…334d

0xd32edf…ff58

17 touches
36 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0xcb45d9d6…cb86

0x1b6862…e19c

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001e

0x1b6862…e19c

6 touches
3 conflicts

0x1e28635a…ba38

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

36 conflicts on slot 0x5685e87494…bb334d

← previous block·next block →recent activity