← previous blocknext block →recent activity

Analyzing

Block #74,773,233

17 transactions · 13 stateful · 2026-05-15 14:53:42 UTC

Parallelism

88/100

Blocked

38%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,773,233  ·  17 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

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x631b4113…baa9

0x34b655…2a6f

4 touches
1 conflict

0x4661f8ba…d356

0x065c9d…c394

3 touches
1 conflict

0x15007455…ed03

0x34b655…2a6f

2 touches
0 conflicts

0x150af51d…9c42

0x34b655…2a6f

2 touches
0 conflicts

0x664bf99e…0a8c

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x046a928e85…e50012

← previous block·next block →recent activity