← previous blocknext block →recent activity

Analyzing

Block #73,804,732

32 transactions · 24 stateful · 2026-05-11 03:15:05 UTC

Parallelism

75/100

Blocked

58%

Avg conflicts / tx

1.38

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,804,732  ·  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

0x2c6ce2aa…8d19

0xd32edf…ff58

15 touches
28 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x468c69b1…af11

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1ae

0x8d66a4…3095

6 touches
3 conflicts

0x00000000…001e

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002e

0x1b6862…e19c

4 touches
1 conflict

0x14d1bf0e…e09f

0x1b6862…e19c

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

28 conflicts on slot 0x2c6ce2aabb…868d19

← previous block·next block →recent activity