← previous blocknext block →recent activity

Analyzing

Block #74,332,596

21 transactions · 14 stateful · 2026-05-13 13:50:09 UTC

Parallelism

86/100

Blocked

21%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,332,596  ·  21 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

0xf0f418cb…a92e

0xd32edf…ff58

5 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x35ab3abf…7b91

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x09beabbc…065c

0x188d58…ea8e

2 touches
0 conflicts

0x09beabbc…065e

0x188d58…ea8e

2 touches
0 conflicts

0x46cb45de…a566

0x188d58…ea8e

2 touches
0 conflicts

0x46cb45de…a568

0x188d58…ea8e

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: 0xd32edf66…9fff58

3 conflicts on slot 0xf0f418cb89…b5a92e

← previous block·next block →recent activity