← previous blocknext block →recent activity

Analyzing

Block #74,415,964

13 transactions · 12 stateful · 2026-05-13 23:04:54 UTC

Parallelism

85/100

Blocked

17%

Avg conflicts / tx

0.23

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,415,964  ·  13 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

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x0cfe5002…be5a

0xd32edf…ff58

3 touches
1 conflict

0x02836062…7853

0x065c9d…c394

2 touches
1 conflict

0xc04dd329…f4c1

0x065c9d…c394

2 touches
1 conflict

0x76e559a4…77fb

0x2a68ba…90c5

2 touches
0 conflicts

0x0d622e34…0000

0x681e90…ae09

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: 0xab35264b…1cfa38

1 conflict on slot 0x0000000000…000002

← previous block·next block →recent activity