← previous blocknext block →recent activity

Analyzing

Block #74,450,385

14 transactions · 11 stateful · 2026-05-14 02:54:03 UTC

Parallelism

79/100

Blocked

18%

Avg conflicts / tx

0.14

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,450,385  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xa3ff1ab2…8ae3

0x34b655…2a6f

4 touches
1 conflict

0xb8228d38…3953

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0f418e62…25fd

0x34b655…2a6f

2 touches
0 conflicts

0x1c389468…6b0e

0x34b655…2a6f

2 touches
0 conflicts

0x5b61a509…accb

0x34b655…2a6f

2 touches
0 conflicts

0x79d53a28…6a9e

0x34b655…2a6f

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