← previous blocknext block →recent activity

Analyzing

Block #74,456,004

16 transactions · 7 stateful · 2026-05-14 03:31:30 UTC

Parallelism

88/100

Blocked

14%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,456,004  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0x0f418e62…25fd

0x34b655…2a6f

4 touches
1 conflict

0xa3ff1ab2…8ae3

0x34b655…2a6f

4 touches
1 conflict

0xb8228d38…3953

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0872abbe…9c39

0x2a68ba…90c5

2 touches
0 conflicts

0x06cdf7f0…fbe6

0x3bd359…433a

2 touches
0 conflicts

0xb9eb1318…ce53

0x3bd359…433a

2 touches
0 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: 0x34b6552d…112a6f

1 conflict on slot 0xf3981be56e…f02c47

← previous block·next block →recent activity