← previous blocknext block →recent activity

Analyzing

Block #74,520,028

16 transactions · 13 stateful · 2026-05-14 10:39:06 UTC

Parallelism

88/100

Blocked

23%

Avg conflicts / tx

0.19

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,520,028  ·  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

0xb6599b96…1024

0x065c9d…c394

4 touches
1 conflict

0xedb848fe…6534

0x34b655…2a6f

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x2cf96c0a…538a

0x34b655…2a6f

4 touches
1 conflict

0x874f5c70…608f

0x34b655…2a6f

4 touches
1 conflict

0x908d4442…2c4b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x27f841ae…5224

0x065c9d…c394

3 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: 0x065c9d28…a9c394

1 conflict on slot 0xb6599b968d…d51024

← previous block·next block →recent activity