← previous blocknext block →recent activity

Analyzing

Block #74,635,455

34 transactions · 28 stateful · 2026-05-14 23:33:42 UTC

Parallelism

74/100

Blocked

57%

Avg conflicts / tx

1.44

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,635,455  ·  34 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

0x2fc37035…3004

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0xf3981be5…2c47

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c6

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

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

36 conflicts on slot 0x2fc3703524…f33004

← previous block·next block →recent activity