← previous blocknext block →recent activity

Analyzing

Block #74,464,695

16 transactions · 9 stateful · 2026-05-14 04:29:20 UTC

Parallelism

88/100

Blocked

11%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,464,695  ·  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

0xd49762c9…1359

0x34b655…2a6f

4 touches
1 conflict

0x908d4442…2c4b

0x34b655…2a6f

4 touches
1 conflict

0xc6417de0…2191

0xc8689a…ee79

4 touches
1 conflict

0x0711ec2d…d973

0x34b655…2a6f

2 touches
0 conflicts

0x4118ae27…23f9

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

2 touches
0 conflicts

0x8a85cf3d…2868

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 0xd49762c96f…3b1359

← previous block·next block →recent activity